User interface for loyalty accounts and private label accounts

ABSTRACT

The present disclosure generally relates to the use of loyalty accounts, private label payment accounts, and general payment accounts using an electronic device with an electronic wallet. Various accounts are linked to the electronic device. In some examples, the electronic device is NFC-enabled. The electronic device may be used to provide loyalty account information and payment account information to a payment terminal, such as an NFC-enabled payment terminal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/814,226, entitled “USER INTERFACE FOR LOYALTY ACCOUNTS AND PRIVATELABEL ACCOUNTS,” filed Mar. 10, 2020, which is a continuation of U.S.patent application Ser. No. 14/871,635, entitled “USER INTERFACE FORLOYALTY ACCOUNTS AND PRIVATE LABEL ACCOUNTS,” filed Sep. 30, 2015, whichis a continuation of U.S. patent application Ser. No. 14/869,715,entitled “USER INTERFACE FOR LOYALTY ACCOUNTS AND PRIVATE LABELACCOUNTS,” filed Sep. 29, 2015, which claims priority from U.S.Provisional Ser. No. 62/230,441, entitled “USER INTERFACE FOR LOYALTYACCOUNTS AND PRIVATE LABEL ACCOUNTS,” filed Jun. 5, 2015, each of whichis hereby incorporated by reference in its entirety for all purposes.

This application relates to the following provisional applications: U.S.Patent Application Ser. No. 62/004,886, entitled “USER INTERFACE FORPAYMENTS”, filed May 29, 2014, (Reference No. P22848USP1); U.S. PatentApplication Ser. No. 62/047,545, entitled “USER INTERFACE FOR PAYMENTS”,filed Sep. 8, 2014, (Reference No. P22848USP2); U.S. Patent ApplicationSer. No. 62/127,790, entitled “USER INTERFACE FOR PAYMENTS”, filed Mar.3, 2015, (Reference No. P22848USP3); and U.S. Patent Application Ser.No. 62/110,566, entitled “USER INTERFACE FOR PAYMENTS”, filed Feb. 1,2015, (Reference No. P26049USP1); U.S. Patent Application Ser. No.61/912,727, entitled “PROVISIONING AND AUTHENTICATING CREDENTIALS ON ANELECTRONIC DEVICE”, filed Dec. 6, 2013, (Reference No. P19543USP1); U.S.Patent Application Ser. No. 61/909,717, entitled “PROVISIONING OFCREDENTIALS ON AN ELECTRONIC DEVICE USING PASSWORDS COMMUNICATED OVERVERIFIED CHANNELS”, filed Nov. 27, 2013, (Reference No. P19950USP1);U.S. Patent Application Ser. No. 62/004,182, entitled “ONLINE PAYMENTSUSING A SECURE ELEMENT OF AN ELECTRONIC DEVICE”, filed May 28, 2014,(Reference No. P20450USP4); U.S. Patent Application Ser. No. 61/920,029,entitled “DELETION OF CREDENTIALS FROM AN ELECTRONIC DEVICE”, filed Dec.23, 2013, (Reference No. P21084USP1); U.S. Patent Application Ser. No.61/899,737, entitled “USING BIOAUTHENTICATION INNEAR-FIELD-COMMUNICATION TRANSACTIONS”, filed Nov. 4, 2013, (ReferenceNo. P21646USP1); U.S. Patent Application Ser. No. 61/905,035, entitled“GENERATING TRANSACTION IDENTIFIERS”, filed Nov. 15, 2013, (ReferenceNo. P21714USP1); U.S. Patent Application Ser. No. 61/905,042, entitled“ELECTRONIC RECEIPTS FOR NFC-BASED FINANCIAL TRANSACTIONS”, filed Nov.15, 2013, (Reference No. 21734USP1); U.S. Patent Application Ser. No.62/004,798, entitled “FINANCIAL-TRANSACTION NOTIFICATIONS”, filed May29, 2014, (Reference No. P23211USP1); U.S. Patent Application Ser. No.62/004,837, entitled “METHODS FOR MANAGING PAYMENT APPLETS ON A SECUREELEMENT TO CONDUCT MOBILE PAYMENT TRANSACTIONS”, filed May 29, 2014,(Reference No. P23215USP1); U.S. Patent Application Ser. No. 62/004,840,entitled “METHODS FOR OPERATING A PORTABLE ELECTRONIC DEVICE TO CONDUCTMOBILE PAYMENT TRANSACTIONS”, filed May 29, 2014, (Reference No.P23223USP1); U.S. Patent Application Ser. No. 62/004,835, entitled“METHODS FOR USING A PRIMARY USER DEVICE TO PROVISION CREDENTIALS ONTO ASECONDARY USER DEVICE”, filed May 29, 2014, (Reference No. P23224USP1);U.S. Patent Application Ser. No. 62/004,832, entitled “METHODS FOR USINGA RANDOM AUTHORIZATION NUMBER TO PROVIDE ENHANCED SECURITY FOR A SECUREELEMENT”, filed May 29, 2014, (Reference No. P23261USP1); U.S. PatentApplication Ser. No. 62/004,338, entitled “USER DEVICE SECUREPARTICIPATION IN TRANSACTIONS VIA LOCAL SECURE ELEMENT DETECTION OFMECHANICAL INPUT”, filed May 29, 2014, (Reference No. P22931USP1); andU.S. Utility patent application Ser. No. 14/092,205, entitled “SECUREPROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE”, filed Nov. 27,2013, (Reference No. P19545US1); each of which is hereby incorporated byreference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to computer user interfaces associated withloyalty accounts and payment accounts.

BACKGROUND

The use of electronic devices for making payments and providing loyaltyaccount information at point-of-sale terminals and over the Internet hasincreased significantly in recent years. Exemplary point-of-saleterminals include Near Field Communication-enabled (NFC-enabled)terminals, bluetooth-enabled terminals, and barcode scanner-enabledterminals. Electronic devices can be used in conjunction with theseexemplary terminals to enable the user of the electronic device to makea payment for the purchase of, for example, a good or service and/or toprovide loyalty account information.

BRIEF SUMMARY

Some techniques for linking accounts to an electronic device, selectingan account for use in a transaction, and transmitting accountinformation in a transaction, however, are generally cumbersome andinefficient. For example, existing techniques use a complex andtime-consuming user interface, which may include multiple key presses orkeystrokes. Existing techniques require more time than necessary,wasting user time and device energy. This latter consideration isparticularly important in battery-operated devices.

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for linking accounts to an electronicdevice, selecting an account for use in a transaction, and transmittingaccount information in a transaction. Such methods and interfacesoptionally complement or replace other methods for performing similartasks. Such methods and interfaces reduce the cognitive burden on a userand produce a more efficient human-machine interface. Forbattery-operated computing devices, such methods and interfaces conservepower and increase the time between battery charges.

In some embodiments, a method is described the method, comprising: at anelectronic device with a display and one or more wireless communicationelements: transmitting, using the one or more wireless communicationelements, payment account information to a payment terminal that isproximate to the electronic device, wherein the payment accountinformation enables the payment terminal to engage in a paymenttransaction; subsequent to engaging in the payment transaction with thepayment terminal, receiving, from a remote source, loyalty informationof a loyalty account; displaying, on the display, a linking affordance;receiving user input corresponding to an activation of the linkingaffordance; and in response to receiving the user input, displaying, onthe display, a user interface for linking the loyalty account to theelectronic device.

In some embodiments, a non-transitory computer-readable medium isdescribed, the non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device with a display and one or more wirelesscommunication elements, the one or more programs including instructionswhich, when executed by the one or more processors, cause the electronicdevice to: transmit, using the one or more wireless communicationelements, payment account information to a payment terminal that isproximate to the electronic device, wherein the payment accountinformation enables the payment terminal to engage in a paymenttransaction; subsequent to engaging in the payment transaction with thepayment terminal, receive, from a remote source, loyalty information ofa loyalty account; display, on the display, a linking affordance;receive user input corresponding to an activation of the linkingaffordance; and in response to receiving the user input, display, on thedisplay, a user interface for linking the loyalty account to theelectronic device.

In some embodiments, a transitory computer-readable medium is described,the transitory computer-readable storage medium comprising one or moreprograms for execution by one or more processors of an electronic devicewith a display and one or more wireless communication elements, the oneor more programs including instructions which, when executed by the oneor more processors, cause the electronic device to: transmit, using theone or more wireless communication elements, payment account informationto a payment terminal that is proximate to the electronic device,wherein the payment account information enables the payment terminal toengage in a payment transaction; subsequent to engaging in the paymenttransaction with the payment terminal, receive, from a remote source,loyalty information of a loyalty account; display, on the display, alinking affordance; receive user input corresponding to an activation ofthe linking affordance; and in response to receiving the user input,display, on the display, a user interface for linking the loyaltyaccount to the electronic device.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display; one or more wireless communicationelements; one or more processors; memory; and one or more programsstored in memory, including instructions which, when executed by the oneor more processors, cause the electronic device to: transmit, using theone or more wireless communication elements, payment account informationto a payment terminal that is proximate to the electronic device,wherein the payment account information enables the payment terminal toengage in a payment transaction; subsequent to engaging in the paymenttransaction with the payment terminal, receive, from a remote source,loyalty information of a loyalty account; display, on the display, alinking affordance; receive user input corresponding to an activation ofthe linking affordance; and in response to receiving the user input,display, on the display, a user interface for linking the loyaltyaccount to the electronic device.

In some embodiments, a method is described, the method comprising: at anelectronic device including one or more wireless communication elementsand one or more input devices: receiving, via the one or more wirelesscommunication elements, from a contactless payment terminal that isproximate to the electronic device, a request for loyalty accountinformation for a payment transaction for which authorization to proceedhas been provided via the one or more input devices of the electronicdevice; and in response to receiving the request for loyalty accountinformation: determining whether a loyalty-sharing condition is met; inaccordance with a determination that the loyalty-sharing condition ismet, transmitting loyalty account information of a loyalty account tothe contactless payment terminal via the one or more wirelesscommunication elements; and in accordance with a determination that theloyalty-sharing condition is not met, forgoing transmitting loyaltyaccount information of the loyalty account to the contactless paymentterminal.

In some embodiments, a non-transitory computer-readable storage mediumis described, the non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device with one or more wireless communication elementsand one or more input devices, the one or more programs includinginstructions which, when executed by the one or more processors, causethe electronic device to: receive, via the one or more wirelesscommunication elements, from a contactless payment terminal that isproximate to the electronic device, a request for loyalty accountinformation for a payment transaction for which authorization to proceedhas been provided via the one or more input devices of the electronicdevice; and in response to receiving the request for loyalty accountinformation: determine whether a loyalty-sharing condition is met; inaccordance with a determination that the loyalty-sharing condition ismet, transmit loyalty account information of a loyalty account to thecontactless payment terminal via the one or more wireless communicationelements; and in accordance with a determination that theloyalty-sharing condition is not met, forgo transmitting loyalty accountinformation of the loyalty account to the contactless payment terminal.

In some embodiments, a transitory computer-readable storage medium isdescribed, the transitory computer-readable storage medium comprisingone or more programs for execution by one or more processors of anelectronic device with one or more wireless communication elements andone or more input devices, the one or more programs includinginstructions which, when executed by the one or more processors, causethe electronic device to: receive, via the one or more wirelesscommunication elements, from a contactless payment terminal that isproximate to the electronic device, a request for loyalty accountinformation for a payment transaction for which authorization to proceedhas been provided via the one or more input devices of the electronicdevice; and in response to receiving the request for loyalty accountinformation: determine whether a loyalty-sharing condition is met; inaccordance with a determination that the loyalty-sharing condition ismet, transmit loyalty account information of a loyalty account to thecontactless payment terminal via the one or more wireless communicationelements; and in accordance with a determination that theloyalty-sharing condition is not met, forgo transmitting loyalty accountinformation of the loyalty account to the contactless payment terminal.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; one ormore input devices; one or more processors; memory; and one or moreprograms stored in memory, including instructions which, when executedby the one or more processors, cause the electronic device to: receive,via the one or more wireless communication elements, from a contactlesspayment terminal that is proximate to the electronic device, a requestfor loyalty account information for a payment transaction for whichauthorization to proceed has been provided via the one or more inputdevices of the electronic device; and in response to receiving therequest for loyalty account information: determine whether aloyalty-sharing condition is met; in accordance with a determinationthat the loyalty-sharing condition is met, transmit loyalty accountinformation of a loyalty account to the contactless payment terminal viathe one or more wireless communication elements; and in accordance witha determination that the loyalty-sharing condition is not met, forgotransmitting loyalty account information of the loyalty account to thecontactless payment terminal.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; one ormore input devices one or more processors; means for receiving, via theone or more wireless communication elements, from a contactless paymentterminal that is proximate to the electronic device, a request forloyalty account information for a payment transaction for whichauthorization to proceed has been provided via the one or more inputdevices of the electronic device; and means, responsive to receiving therequest for loyalty account information, for: determining whether aloyalty-sharing condition is met; in accordance with a determinationthat the loyalty-sharing condition is met, transmitting loyalty accountinformation of a loyalty account to the contactless payment terminal viathe one or more wireless communication elements; and in accordance witha determination that the loyalty-sharing condition is not met, forgoingtransmitting loyalty account information of the loyalty account to thecontactless payment terminal.

In some embodiments, a method is described, the method comprising: at anelectronic device with one or more wireless communication elements and adisplay: receiving, via the one or more wireless communication elements,information about a payment transaction for which a loyalty account isavailable to be used; in response to receiving the information about thepayment transaction, concurrently displaying, on the display: anindication of a payment account for the payment transaction; and anindication of the loyalty account for the payment transaction.

In some embodiments, a non-transitory computer-readable storage mediumis described, the non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device with one or more wireless communication elementsand a display, the one or more programs including instructions which,when executed by the one or more processors, cause the electronic deviceto: receive, via the one or more wireless communication elements,information about a payment transaction for which a loyalty account isavailable to be used; in response to receiving the information about thepayment transaction, concurrently display, on the display: an indicationof a payment account for the payment transaction; and an indication ofthe loyalty account for the payment transaction.

In some embodiments, a transitory computer-readable storage medium isdescribed, the transitory computer-readable storage medium comprisingone or more programs for execution by one or more processors of anelectronic device with one or more wireless communication elements and adisplay, the one or more programs including instructions which, whenexecuted by the one or more processors, cause the electronic device to:receive, via the one or more wireless communication elements,information about a payment transaction for which a loyalty account isavailable to be used; in response to receiving the information about thepayment transaction, concurrently display, on the display: an indicationof a payment account for the payment transaction; and an indication ofthe loyalty account for the payment transaction.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; adisplay; one or more processors; memory; and one or more programs storedin memory, including instructions which, when executed by the one ormore processors, cause the electronic device to: receive, via the one ormore wireless communication elements, information about a paymenttransaction for which a loyalty account is available to be used; inresponse to receiving the information about the payment transaction,concurrently display, on the display: an indication of a payment accountfor the payment transaction; and an indication of the loyalty accountfor the payment transaction.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; adisplay; means for receiving, via the one or more wireless communicationelements, information about a payment transaction for which a loyaltyaccount is available to be used; means, responsive to receiving theinformation about the payment transaction, for concurrently displaying,on the display: an indication of a payment account for the paymenttransaction; and an indication of the loyalty account for the paymenttransaction.

In some embodiments, a method is described, the method comprising: at anelectronic device with one or more wireless communication elements:receiving, from a contactless payment terminal via the one or morewireless communication elements, a request associated with a paymenttransaction; determining whether the request comprises a request forpayment using a particular payment account type; in accordance with adetermination that the request does not comprise the request for paymentusing the particular payment account type, proceeding with the paymenttransaction using a default payment account; and in accordance with adetermination that the request comprises the request for payment usingthe particular payment account type: determining whether a paymentaccount selection condition is met; and in accordance with adetermination that the payment account selection condition is not met,forgoing proceeding with the payment transaction using a payment accountof the particular payment account type.

In some embodiments, a non-transitory computer-readable storage mediumis described, the non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device with one or more wireless communicationelements, the one or more programs including instructions which, whenexecuted by the one or more processors, cause the electronic device to:receive, from a contactless payment terminal via the one or morewireless communication elements, a request associated with a paymenttransaction; determine whether the request comprises a request forpayment using a particular payment account type; in accordance with adetermination that the request does not comprise the request for paymentusing the particular payment account type, proceed with the paymenttransaction using a default payment account; and in accordance with adetermination that the request comprises the request for payment usingthe particular payment account type: determine whether a payment accountselection condition is met; and in accordance with a determination thatthe payment account selection condition is not met, forgo proceedingwith the payment transaction using a payment account of the particularpayment account type.

In some embodiments, a transitory computer-readable storage medium isdescribed, the transitory computer-readable storage medium comprisingone or more programs for execution by one or more processors of anelectronic device with one or more wireless communication elements, theone or more programs including instructions which, when executed by theone or more processors, cause the electronic device to: receive, from acontactless payment terminal via the one or more wireless communicationelements, a request associated with a payment transaction; determinewhether the request comprises a request for payment using a particularpayment account type; in accordance with a determination that therequest does not comprise the request for payment using the particularpayment account type, proceed with the payment transaction using adefault payment account; and in accordance with a determination that therequest comprises the request for payment using the particular paymentaccount type: determine whether a payment account selection condition ismet; and in accordance with a determination that the payment accountselection condition is not met, forgo proceeding with the paymenttransaction using a payment account of the particular payment accounttype.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; one ormore processors; memory; and one or more programs stored in memory,including instructions which, when executed by the one or moreprocessors, cause the electronic device to: receive, from a contactlesspayment terminal via the one or more wireless communication elements, arequest associated with a payment transaction; determine whether therequest comprises a request for payment using a particular paymentaccount type; in accordance with a determination that the request doesnot comprise the request for payment using the particular paymentaccount type, proceed with the payment transaction using a defaultpayment account; and in accordance with a determination that the requestcomprises the request for payment using the particular payment accounttype: determine whether a payment account selection condition is met;and in accordance with a determination that the payment accountselection condition is not met, forgo proceeding with the paymenttransaction using a payment account of the particular payment accounttype.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; meansfor receiving, from a contactless payment terminal via the one or morewireless communication elements, a request associated with a paymenttransaction; means for determining whether the request comprises arequest for payment using a particular payment account type; means, inaccordance with a determination that the request does not comprise therequest for payment using the particular payment account type, forproceeding with the payment transaction using a default payment account;and means, in accordance with a determination that the request comprisesthe request for payment using the particular payment account type, for:determining whether a payment account selection condition is met; and inaccordance with a determination that the payment account selectioncondition is not met, forgoing proceeding with the payment transactionusing a payment account of the particular payment account type.

In some embodiments, a method is described, the method comprising: at anelectronic device with a location sensor and a display: detecting, usingthe location sensor, that a current location is associated withprompting for use of a particular payment account; in response todetecting that the current location is associated with prompting for useof the particular payment account: determining whether the electronicdevice has previously received an indication of a user preferenceassociated with using the particular payment account at the currentlocation; in accordance with a determination that the device haspreviously received an indication of the user preference associated withusing the particular payment account at the current location,displaying, on the display, a visual indication that the particularpayment account is available for use at the location; and in accordancewith a determination that the device has not previously received anindication of the user preference associated with using the particularpayment account at the current location, forgoing displaying, on thedisplay, the visual indication that the particular payment account isavailable for use at the location.

In some embodiments, a non-transitory computer-readable storage mediumis described, the non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device with a location sensor and a display, the one ormore programs including instructions which, when executed by the one ormore processors, cause the electronic device to: detect, using thelocation sensor, that a current location is associated with promptingfor use of a particular payment account; in response to detecting thatthe current location is associated with prompting for use of theparticular payment account: determine whether the electronic device haspreviously received an indication of a user preference associated withusing the particular payment account at the current location; inaccordance with a determination that the device has previously receivedan indication of the user preference associated with using theparticular payment account at the current location, display, on thedisplay, a visual indication that the particular payment account isavailable for use at the location; and in accordance with adetermination that the device has not previously received an indicationof the user preference associated with using the particular paymentaccount at the current location, forgo displaying, on the display, thevisual indication that the particular payment account is available foruse at the location.

In some embodiments, a transitory computer-readable storage medium isdescribed, the transitory computer-readable storage medium comprisingone or more programs for execution by one or more processors of anelectronic device with a location sensor and a display, the one or moreprograms including instructions which, when executed by the one or moreprocessors, cause the electronic device to: detect, using the locationsensor, that a current location is associated with prompting for use ofa particular payment account; in response to detecting that the currentlocation is associated with prompting for use of the particular paymentaccount: determine whether the electronic device has previously receivedan indication of a user preference associated with using the particularpayment account at the current location; in accordance with adetermination that the device has previously received an indication ofthe user preference associated with using the particular payment accountat the current location, display, on the display, a visual indicationthat the particular payment account is available for use at thelocation; and in accordance with a determination that the device has notpreviously received an indication of the user preference associated withusing the particular payment account at the current location, forgodisplaying, on the display, the visual indication that the particularpayment account is available for use at the location.

In some embodiments, an electronic device is described, the electronicdevice comprising: a location sensor; a display; one or more processors;memory; and one or more programs stored in memory, includinginstructions which, when executed by the one or more processors, causethe electronic device to: detect, using the location sensor, that acurrent location is associated with prompting for use of a particularpayment account; in response to detecting that the current location isassociated with prompting for use of the particular payment account:determine whether the electronic device has previously received anindication of a user preference associated with using the particularpayment account at the current location; in accordance with adetermination that the device has previously received an indication ofthe user preference associated with using the particular payment accountat the current location, display, on the display, a visual indicationthat the particular payment account is available for use at thelocation; and in accordance with a determination that the device has notpreviously received an indication of the user preference associated withusing the particular payment account at the current location, forgodisplaying, on the display, the visual indication that the particularpayment account is available for use at the location.

In some embodiments, an electronic device is described, the electronicdevice comprising: a location sensor; a display; means for detecting,using the location sensor, that a current location is associated withprompting for use of a particular payment account; means, responsive todetecting that the current location is associated with prompting for useof the particular payment account, for: determining whether theelectronic device has previously received an indication of a userpreference associated with using the particular payment account at thecurrent location; in accordance with a determination that the device haspreviously received an indication of the user preference associated withusing the particular payment account at the current location,displaying, on the display, a visual indication that the particularpayment account is available for use at the location; and in accordancewith a determination that the device has not previously received anindication of the user preference associated with using the particularpayment account at the current location, forgoing displaying, on thedisplay, the visual indication that the particular payment account isavailable for use at the location.

In some embodiments, a method is described, the method, comprising: atan electronic device with a display and one or more input devices:receiving, via the one or more input devices, a request to link apayment card with the electronic device, the request comprising accountinformation; in response to receiving the request via the one or moreinput devices: determining whether the payment card is associated withmultiple payment accounts; in accordance with a determination that thepayment card is associated with multiple payment accounts, displaying,on the display, a payment account interface for the payment card thatenables user selection among multiple payment accounts of the paymentcard; and in accordance with a determination that the payment card isnot associated with multiple payment accounts, displaying, on thedisplay, a payment account interface for the payment card that does notenable user selection among multiple payment accounts of the paymentcard.

In some embodiments, a non-transitory computer-readable storage mediumis described, the non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device with a display and one or more input devices,the one or more programs including instructions which, when executed bythe one or more processors, cause the electronic device to: receive, viathe one or more input devices, a request to link a payment card with theelectronic device, the request comprising account information; inresponse to receiving the request via the one or more input devices:determine whether the payment card is associated with multiple paymentaccounts; in accordance with a determination that the payment card isassociated with multiple payment accounts, display, on the display, apayment account interface for the payment card that enables userselection among multiple payment accounts of the payment card; and inaccordance with a determination that the payment card is not associatedwith multiple payment accounts, display, on the display, a paymentaccount interface for the payment card that does not enable userselection among multiple payment accounts of the payment card.

In some embodiments, a transitory computer-readable storage medium isdescribed, the transitory computer-readable storage medium comprisingone or more programs for execution by one or more processors of anelectronic device with a display and one or more input devices, the oneor more programs including instructions which, when executed by the oneor more processors, cause the electronic device to: receive, via the oneor more input devices, a request to link a payment card with theelectronic device, the request comprising account information; inresponse to receiving the request via the one or more input devices:determine whether the payment card is associated with multiple paymentaccounts; in accordance with a determination that the payment card isassociated with multiple payment accounts, display, on the display, apayment account interface for the payment card that enables userselection among multiple payment accounts of the payment card; and inaccordance with a determination that the payment card is not associatedwith multiple payment accounts, display, on the display, a paymentaccount interface for the payment card that does not enable userselection among multiple payment accounts of the payment card.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display and one; more input devices; one or moreprocessors; memory; and one or more programs stored in memory, includinginstructions which, when executed by the one or more processors, causethe electronic device to: receive, via the one or more input devices, arequest to link a payment card with the electronic device, the requestcomprising account information; in response to receiving the request viathe one or more input devices: determine whether the payment card isassociated with multiple payment accounts; in accordance with adetermination that the payment card is associated with multiple paymentaccounts, display, on the display, a payment account interface for thepayment card that enables user selection among multiple payment accountsof the payment card; and in accordance with a determination that thepayment card is not associated with multiple payment accounts, display,on the display, a payment account interface for the payment card thatdoes not enable user selection among multiple payment accounts of thepayment card.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display; one or more input devices; means forreceiving, via the one or more input devices, a request to link apayment card with the electronic device, the request comprising accountinformation; means, responsive to receiving the request via the one ormore input devices, for: determining whether the payment card isassociated with multiple payment accounts; in accordance with adetermination that the payment card is associated with multiple paymentaccounts, displaying, on the display, a payment account interface forthe payment card that enables user selection among multiple paymentaccounts of the payment card; and in accordance with a determinationthat the payment card is not associated with multiple payment accounts,displaying, on the display, a payment account interface for the paymentcard that does not enable user selection among multiple payment accountsof the payment card.

In some embodiments, a method is described, the method comprising: at anelectronic device with a display: displaying a user interface for afinancial application that is one of a plurality of applications on theelectronic device, wherein: the financial application is a third-partyapplication that is associated with a financial institution; and thefinancial application is restricted from accessing a secured area of thedevice that is accessible by a first-party electronic walletapplication; while displaying the user interface for the financialapplication, receiving a request to add a payment account associatedwith the financial institution to the electronic wallet; and in responseto receiving the request to add the payment account associated with thefinancial institution to the electronic wallet and in accordance with adetermination that addition of the payment account to the electronicwallet has been authorized, storing information associated with thepayment account that is provided by the third-party application to thesecured area of the device that is accessible by the first-partyelectronic wallet application.

In some embodiments, a non-transitory computer-readable storage mediumis described, the non-transitory computer-readable storage mediumcomprising one or more programs for execution by one or more processorsof an electronic device with a display, the one or more programsincluding instructions which, when executed by the one or moreprocessors, cause the electronic device to: display, on the display, auser interface for a financial application that is one of a plurality ofapplications on the electronic device, wherein: the financialapplication is a third-party application that is associated with afinancial institution; and the financial application is restricted fromaccessing a secured area of the device that is accessible by afirst-party electronic wallet application; while displaying the userinterface for the financial application, receive a request to add apayment account associated with the financial institution to theelectronic wallet; and in response to receiving the request to add thepayment account associated with the financial institution to theelectronic wallet and in accordance with a determination that additionof the payment account to the electronic wallet has been authorized,store information associated with the payment account that is providedby the third-party application to the secured area of the device that isaccessible by the first-party electronic wallet application.

In some embodiments, a transitory computer-readable storage medium isdescribed, the transitory computer-readable storage medium comprisingone or more programs for execution by one or more processors of anelectronic device with a display, the one or more programs includinginstructions which, when executed by the one or more processors, causethe electronic device to: display, on the display, a user interface fora financial application that is one of a plurality of applications onthe electronic device, wherein: the financial application is athird-party application that is associated with a financial institution;and the financial application is restricted from accessing a securedarea of the device that is accessible by a first-party electronic walletapplication; while displaying the user interface for the financialapplication, receive a request to add a payment account associated withthe financial institution to the electronic wallet; and in response toreceiving the request to add the payment account associated with thefinancial institution to the electronic wallet and in accordance with adetermination that addition of the payment account to the electronicwallet has been authorized, store information associated with thepayment account that is provided by the third-party application to thesecured area of the device that is accessible by the first-partyelectronic wallet application.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display; one or more processors; memory; and one ormore programs stored in memory, including instructions which, whenexecuted by the one or more processors, cause the electronic device to:display, on the display, a user interface for a financial applicationthat is one of a plurality of applications on the electronic device,wherein: the financial application is a third-party application that isassociated with a financial institution; and the financial applicationis restricted from accessing a secured area of the device that isaccessible by a first-party electronic wallet application; whiledisplaying the user interface for the financial application, receive arequest to add a payment account associated with the financialinstitution to the electronic wallet; and in response to receiving therequest to add the payment account associated with the financialinstitution to the electronic wallet and in accordance with adetermination that addition of the payment account to the electronicwallet has been authorized, store information associated with thepayment account that is provided by the third-party application to thesecured area of the device that is accessible by the first-partyelectronic wallet application.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display; means for displaying a user interface fora financial application that is one of a plurality of applications onthe electronic device, wherein: the financial application is athird-party application that is associated with a financial institution;and the financial application is restricted from accessing a securedarea of the device that is accessible by a first-party electronic walletapplication; means, while displaying the user interface for thefinancial application, for receiving a request to add a payment accountassociated with the financial institution to the electronic wallet; andmeans, responsive to receiving the request to add the payment accountassociated with the financial institution to the electronic wallet andin accordance with a determination that addition of the payment accountto the electronic wallet has been authorized, for storing informationassociated with the payment account that is provided by the third-partyapplication to the secured area of the device that is accessible by thefirst-party electronic wallet application.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display unit; one or more wireless communicationelements; and a processing unit configured to: transmit, using the oneor more wireless communication elements, payment account information toa payment terminal that is proximate to the electronic device, whereinthe payment account information enables the payment terminal to engagein a payment transaction; subsequent to engaging in the paymenttransaction with the payment terminal, receive, from a remote source,loyalty information of a loyalty account; enable display of, on thedisplay unit, a linking affordance; receive user input corresponding toan activation of the linking affordance; and in response to receivingthe user input, enable display of, on the display unit, a user interfacefor linking the loyalty account to the electronic device.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; one ormore input devices; and a processing unit configured to: receive, viathe one or more wireless communication elements, from a contactlesspayment terminal that is proximate to the electronic device, a requestfor loyalty account information for a payment transaction for whichauthorization to proceed has been provided via the one or more inputdevices of the electronic device; and in response to receiving therequest for loyalty account information: determine whether aloyalty-sharing condition is met; in accordance with a determinationthat the loyalty-sharing condition is met, transmit loyalty accountinformation of a loyalty account to the contactless payment terminal viathe one or more wireless communication elements; and in accordance witha determination that the loyalty-sharing condition is not met, forgotransmitting loyalty account information of the loyalty account to thecontactless payment terminal.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; adisplay unit; and a processing unit configured to: receive, via the oneor more wireless communication elements, information about a paymenttransaction for which a loyalty account is available to be used; inresponse to receiving the information about the payment transaction,concurrently enable display of, on the display unit: an indication of apayment account for the payment transaction; and an indication of theloyalty account for the payment transaction.

In some embodiments, an electronic device is described, the electronicdevice comprising: one or more wireless communication elements; and aprocessing unit configured to: receive, from a contactless paymentterminal via the one or more wireless communication elements, a requestassociated with a payment transaction; determine whether the requestcomprises a request for payment using a particular payment account type;in accordance with a determination that the request does not comprisethe request for payment using the particular payment account type,proceed with the payment transaction using a default payment account;and in accordance with a determination that the request comprises therequest for payment using the particular payment account type: determinewhether a payment account selection condition is met; and in accordancewith a determination that the payment account selection condition is notmet, forgo proceeding with the payment transaction using a paymentaccount of the particular payment account type.

In some embodiments, an electronic device is described, the electronicdevice comprising: a location sensor; a display unit; and a processingunit configured to: detect, using the location sensor, that a currentlocation is associated with prompting for use of a particular paymentaccount; in response to detecting that the current location isassociated with prompting for use of the particular payment account:determine whether the electronic device has previously received anindication of a user preference associated with using the particularpayment account at the current location; in accordance with adetermination that the device has previously received an indication ofthe user preference associated with using the particular payment accountat the current location, enable display of, on the display unit, avisual indication that the particular payment account is available foruse at the location; and in accordance with a determination that thedevice has not previously received an indication of the user preferenceassociated with using the particular payment account at the currentlocation, forgo enabling display of, on the display unit, the visualindication that the particular payment account is available for use atthe location.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display unit; one or more input devices; and aprocessing unit configured to: receive, via the one or more inputdevices, a request to link a payment card with the electronic device,the request comprising account information; in response to receiving therequest via the one or more input devices: determine whether the paymentcard is associated with multiple payment accounts; in accordance with adetermination that the payment card is associated with multiple paymentaccounts, enable display of, on the display unit, a payment accountinterface for the payment card that enables user selection amongmultiple payment accounts of the payment card; and in accordance with adetermination that the payment card is not associated with multiplepayment accounts, enable display of, on the display unit, a paymentaccount interface for the payment card that does not enable userselection among multiple payment accounts of the payment card.

In some embodiments, an electronic device is described, the electronicdevice comprising: a display unit; and a processing unit configured to:enable display of a user interface for a financial application that isone of a plurality of applications on the electronic device, wherein:the financial application is a third-party application that isassociated with a financial institution; and the financial applicationis restricted from accessing a secured area of the device that isaccessible by a first-party electronic wallet application; whileenabling display of the user interface for the financial application,receive a request to add a payment account associated with the financialinstitution to the electronic wallet; and in response to receiving therequest to add the payment account associated with the financialinstitution to the electronic wallet and in accordance with adetermination that addition of the payment account to the electronicwallet has been authorized, store information associated with thepayment account that is provided by the third-party application to thesecured area of the device that is accessible by the first-partyelectronic wallet application.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for linking accounts to the device, selecting an account foruse in a transaction, and transmitting account information in atransaction, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for performing similar tasks.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 5C illustrates exemplary devices connected via one or morecommunication channels to complete a payment transaction in accordancewith some embodiments.

FIGS. 6A-6F illustrate exemplary techniques and exemplary userinterfaces for linking an account to an electronic device, in accordancewith some embodiments.

FIG. 7 is a flow diagram illustrating a method for linking an account toan electronic device, in accordance with some embodiments.

FIGS. 8A-8H illustrate exemplary techniques and exemplary userinterfaces for providing loyalty account information to a paymentterminal, in accordance with some embodiments.

FIG. 9 is a flow diagram illustrating a method for providing loyaltyaccount information to a payment terminal, in accordance with someembodiments.

FIGS. 10A-10C illustrate exemplary techniques and exemplary userinterfaces for displaying indications of payment accounts and loyaltyaccounts for a payment transaction, in accordance with some embodiments.

FIG. 11 is a flow diagram illustrating a method for displayingindications of payment accounts and loyalty accounts for a paymenttransaction, in accordance with some embodiments.

FIGS. 12A-12E illustrate exemplary techniques and exemplary userinterfaces for proceeding with a payment transaction using a paymentaccount of a requested payment account type, in accordance with someembodiments.

FIG. 13 is a flow diagram illustrating a method for proceeding with apayment transaction using a payment account of a requested paymentaccount type, in accordance with some embodiments.

FIGS. 14A-14E illustrate exemplary techniques and exemplary userinterfaces for providing indications of payments accounts for use atparticular locations, in accordance with some embodiments.

FIG. 15 is a flow diagram illustrating a method for providingindications of payments accounts for use at particular locations, inaccordance with some embodiments.

FIGS. 16A-16G illustrate exemplary techniques and exemplary userinterfaces for displaying multiple payment accounts grouped together, inaccordance with some embodiments.

FIG. 17 is a flow diagram illustrating a method for displaying multiplepayment accounts grouped together, in accordance with some embodiments.

FIGS. 18A-18E illustrate exemplary techniques and exemplary userinterfaces for linking a payment account to an electronic device, inaccordance with some embodiments.

FIG. 19 is a flow diagram illustrating a method for linking a paymentaccount to an electronic device, in accordance with some embodiments.

FIGS. 20-26 illustrate functional block diagrams in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for linking accounts to the electronic device, selectingan account for use in a transaction, and transmitting accountinformation in a transaction. Such techniques can reduce the cognitiveburden on a user who uses the electronic device for making purchases orproviding loyalty account information, thereby enhancing productivity.Further, such techniques can reduce processor and battery powerotherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for linking accounts tothe electronic device, selecting an account for use in a transaction,and transmitting account information in a transaction. FIGS. 6A-6Fillustrate exemplary techniques and exemplary user interfaces forlinking an account to an electronic device. FIG. 7 is a flow diagramillustrating a method for linking an account to an electronic device.The user interfaces of FIGS. 6A-6F are used to illustrate the processesin FIG. 7. FIGS. 8A-8H illustrate exemplary techniques and exemplaryuser interfaces for providing loyalty account information to a paymentterminal. FIG. 9 is a flow diagram illustrating a method for providingloyalty account information to a payment terminal. The user interfacesof FIGS. 8A-8H are used to illustrate the processes in FIG. 9. FIGS.10A-10C illustrate exemplary techniques and exemplary user interfacesfor displaying indications of payment accounts and loyalty accounts fora payment transaction. FIG. 11 is a flow diagram illustrating a methodfor displaying indications of payment accounts and loyalty accounts fora payment transaction. The user interfaces of FIGS. 10A-10C are used toillustrate the processes in FIG. 11. FIGS. 12A-12E illustrate exemplarytechniques and exemplary user interfaces for proceeding with a paymenttransaction using a payment account of a requested payment account type.FIG. 13 is a flow diagram illustrating a method for proceeding with apayment transaction using a payment account of a requested paymentaccount type. The user interfaces of FIGS. 12A-12E are used toillustrate the processes in FIG. 13. FIGS. 14A-14E illustrate exemplarytechniques and exemplary user interfaces for providing indications ofpayments accounts for use at particular locations. FIG. 15 is a flowdiagram illustrating a method for providing indications of paymentsaccounts for use at particular locations. The user interfaces of FIGS.14A-14E are used to illustrate the processes in FIG. 15. FIGS. 16A-16Gillustrate exemplary techniques and exemplary user interfaces fordisplaying multiple payment accounts grouped together. FIG. 17 is a flowdiagram illustrating a method for displaying multiple payment accountsgrouped together. The user interfaces of FIGS. 16A-16G are used toillustrate the processes in FIG. 17. FIGS. 18A-18E illustrate exemplarytechniques and exemplary user interfaces for linking a payment accountto an electronic device. FIG. 19 is a flow diagram illustrating a methodfor linking a payment account to an electronic device. The userinterfaces of FIGS. 18A-18E are used to illustrate the processes in FIG.19.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MIMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 700, 900, 1100, 1300,1500, 1700, and 1900 (FIGS. 7, 9, 11, 13, 15, 17, and 19). Thecomputer-executable instructions can also be stored and/or transportedwithin any non-transitory computer-readable storage medium for use by orin connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Forpurposes of this document, a “non-transitory computer-readable storagemedium” can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.5, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIG. 5C illustrates exemplary devices connected via one or morecommunication channels to complete a payment transaction in accordancewith some embodiments. One or more exemplary electronic devices (e.g.,devices 100, 300, and 500) are configured to optionally detect input(e.g., a particular user input, an NFC field) and optionally transmitpayment information (e.g., using NFC). The one or more electronicdevices optionally include NFC hardware and are configured to beNFC-enabled.

The electronic devices (e.g., devices 100, 300, and 500) are optionallyconfigured to store payment account information associated with each ofone or more payment accounts. Payment account information includes, forexample, one or more of: a person's or company's name, a billingaddress, a login, a password, an account number, an expiration date, asecurity code, a telephone number, a bank associated with the paymentaccount (e.g., an issuing bank), and a card network identifier. In someexamples, payment account information includes include an image, such asa picture of a payment card (e.g., taken by the device and/or receivedat the device). In some examples, the electronic devices receive userinput including at least some payment account information (e.g.,receiving user-entered credit, debit, account, or gift card number andexpiration date). In some examples, the electronic devices detect atleast some payment account information from an image (e.g., of a paymentcard captured by a camera sensor of the device). In some examples, theelectronic devices receive at least some payment account informationfrom another device (e.g., another user device or a server). In someexamples, the electronic device receives payment account informationfrom a server associated with another service for which an account for auser or user device previously made a purchase or identified paymentaccount data (e.g., an app for renting or selling audio and/or videofiles).

In some embodiments, a payment account is added to an electronic device(e.g., device 100, 300, and 500), such that payment account informationis securely stored on the electronic device. In some examples, after auser initiates such process, the electronic device transmits informationfor the payment account to a transaction-coordination server, which thencommunicates with a server operated by a payment network for the account(e.g., a payment server) to ensure a validity of the information. Theelectronic device is optionally configured to receive a script from theserver that allows the electronic device to program payment informationfor the account onto the secure element.

In some embodiments, communication among electronic devices 100, 300,and 500 facilitates transactions (e.g., generally or specifictransactions). For example, a first electronic device (e.g., 100) canserve as a provisioning or managing device, and can send notificationsof new or updated payment account data (e.g., information for a newaccount, updated information for an existing account, and/or an alertpertaining to an existing account) to a second electronic device (e.g.,500). In another example, a first electronic device (e.g., 100) can senddata to a second election device, wherein the data reflects informationabout payment transactions facilitated at the first electronic device.The information optionally includes one or more of: a payment amount, anaccount used, a time of purchase, and whether a default account waschanged. The second device (e.g., 500) optionally uses such informationto update a default payment account (e.g., based on a learning algorithmor explicit user input).

Electronic devices (e.g., 100, 300, 500) are configured to communicatewith each over any of a variety of networks. For example, the devicescommunicate using a Bluetooth connection 550 (e.g., which includes atraditional Bluetooth connection or a Bluetooth Low Energy connection)or using a WiFi network 552. Communications among user devices are,optionally, conditioned to reduce the possibility of inappropriatelysharing information across devices. For example, communications relatingto payment information requires that the communicating devices be paired(e.g., be associated with each other via an explicit user interaction)or be associated with a same user account.

In some embodiments, an electronic device (e.g., 100, 300, 500) is usedto communicate with a point-of-sale (POS) payment terminal 610, which isoptionally NFC-enabled. The communication optionally occurs using avariety of communication channels and/or technologies. In one examples,electronic device (e.g., 100, 300, 500) communicates with paymentterminal 610 using an NFC channel 554. In some examples, paymentterminal 610 communicates with an electronic device (e.g., 100, 300,500) using a peer-to-peer NFC mode. Electronic device (e.g., 100, 300,500) is optionally configured transmit a signal to payment terminal 610that includes payment information for a payment account (e.g., a defaultaccount or an account selected for the particular transaction).

In some embodiments, generation of and/or transmission of the signal iscontrolled by a secure element in the electronic device (e.g., 100, 300,500). The secure element optionally requires a particular user inputprior to releasing payment information. For example, the secure elementoptionally requires detection that the electronic device is being worn,detection of a button press, detection of entry of a passcode, detectionof a touch, detection of one or more option selections (e.g., receivedwhile interacting with an application), detection of a fingerprintsignature, detection of a voice or voice command, and or detection of agesture or movement (e.g., rotation or acceleration). In some examples,if a communication channel (e.g., an NFC communication channel) withanother device (e.g., payment terminal 610) is established within adefined time period from detection of the input, the secure elementreleases payment information to be transmitted to the other device(e.g., payment terminal 610). In some examples, the secure element is ahardware component that controls release of secure information. In someexamples, the secure element is a software component that controlsrelease of secure information.

In some embodiments, protocols related to transaction participationdepend on, for example, device types. For example, a condition forgenerating and/or transmitting payment information can be different fora wearable device (e.g., device 500) and a phone (e.g., device 100). Forexample, a generation and/or transmission condition for a wearabledevice includes detecting that a button has been pressed (e.g., after asecurity verification), while a corresponding condition for a phone doesnot require button-depression and instead requires detection ofparticular interaction with an application. In some examples, acondition for transmitting and/or releasing payment information includesreceiving particular input on each of multiple devices. For example,release of payment information optionally requires detection of afingerprint and/or passcode at the device (e.g., device 100) anddetection of a mechanical input (e.g., button press) on another device(e.g., device 500).

Payment terminal 610 optionally uses the payment information to generatea signal to transmit to a payment server 560 to determine whether thepayment is authorized. Payment server 560 optionally includes any deviceor system configured to receive payment information associated with apayment account and to determine whether a proposed purchase isauthorized. In some examples, payment server 560 includes a server of anissuing bank. Payment terminal 610 communicates with payment server 560directly or indirectly via one or more other devices or systems (e.g., aserver of an acquiring bank and/or a server of a card network).

Payment server 560 optionally uses at least some of the paymentinformation to identify a user account from among a database of useraccounts (e.g., 562). For example, each user account includes paymentinformation. An account is, optionally, located by locating an accountwith particular payment information matching that from the POScommunication. In some examples, a payment is denied when providedpayment information is not consistent (e.g., an expiration date does notcorrespond to a credit, debit or gift card number) or when no accountincludes payment information matching that from the POS communication.

In some embodiments, data for the user account further identifies one ormore restrictions (e.g., credit limits); current or previous balances;previous transaction dates, locations and/or amounts; account status(e.g., active or frozen), and/or authorization instructions. In someexamples, the payment server (e.g., 560) uses such data to determinewhether to authorize a payment. For example, a payment server denies apayment when a purchase amount added to a current balance would resultin exceeding an account limit, when an account is frozen, when aprevious transaction amount exceeds a threshold, or when a previoustransaction count or frequency exceeds a threshold.

In some embodiments, payment server 560 responds to POS payment terminal610 with an indication as to whether a proposed purchase is authorizedor denied. In some examples, POS payment terminal 610 transmits a signalto the electronic device (e.g., 100, 300, 500) to identify the result.For example, POS payment terminal 610 sends a receipt to the electronicdevice (e.g., 100, 300, 500) when a purchase is authorized (e.g., via atransaction-coordination server that manages a transaction app on theuser device). In some instances, POS payment terminal 610 presents anoutput (e.g., a visual or audio output) indicative of the result.Payment can be sent to a merchant as part of the authorization processor can be subsequently sent.

In some embodiments, the electronic device (e.g., 100, 300, 500)participates in a transaction that is completed without involvement ofPOS payment terminal 610. For example, upon detecting that a mechanicalinput has been received, a secure element in the electronic device(e.g., 100, 300, 500) releases payment information to allow anapplication on the electronic device to access the information (e.g.,and to transmit the information to a server associated with theapplication).

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100, device 300, or device500.

Some embodiments described below relate to loyalty accounts. Forexample, a loyalty account may be an account of a loyalty program thatprovides a structured marketing effort that rewards customers/members. Aloyalty account is optionally specific to one particular company, store,or chain of stores. A company (such as a retail store or chain ofstores) may use a loyalty account to track purchases or otherinformation about a user (e.g., a purchaser). The loyalty accounttypically entitles the user to a discount on a current or futurepurchase and/or an allotment of points that may be used toward futurepurchases or gifts. In some examples, loyalty accounts cannot be usedfor making payments. Generally, loyalty accounts cannot be used make amonetary payment.

Some embodiments described below relate to private label accounts. Forexample, private label accounts include payment accounts branded for aspecific merchant, independent dealer, or manufacturer. Some privatelabel cards and private label accounts are accepted only at particularmerchants or may provide certain benefits only available at particularmerchants. For example, a particular merchant may offer a private labelaccount to customers that can only be used when making purchases throughthat particular merchant. Merchants frequently prefer to offer privatelabel accounts because it provides customers another way to shop withthe merchant, thus increasing sales and providing customers with aconvenient payment option.

FIGS. 6A-6F illustrate exemplary techniques and exemplary userinterfaces for linking an account, such as a loyalty account, to anelectronic device, in accordance with some embodiments. For example,linking the account to the electronic device places a representation ofthe linked account into an electronic wallet application of theelectronic device and enables the user to subsequently transmit detailsabout the linked account to payment terminals. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 7.

FIGS. 6A-6B illustrate a payment terminal 610 (e.g., a contactlesspayment terminal). The payment terminal 610 may include a keypad 614. Asshown in FIG. 6A, the user may use the keypad 614 to enter a phonenumber or other identification number associated with a particularaccount while conducting a payment transaction. For example, the usermay not have previously linked the loyalty account to the electronicdevice 100, and thus cannot use the electronic device to provide theloyalty account information to the payment terminal 610. Once the userhas entered the phone number or other identification number, the paymentterminal can determine a loyalty account associated with the user. Forexample, a user may encounter a payment terminal requesting loyaltyaccount information at a supermarket or other retail store.Alternatively, the user may not have a loyalty account and may declineto provide any loyalty account information to the payment terminal. Insome embodiments, for a transaction, a user uses a physical loyalty cardthat is scanned, swiped, or otherwise read during the paymenttransaction and associated with the payment transaction.

As shown in FIG. 6B, the payment terminal 610 may also be enabled torequest and receive payments (e.g., based on a payment account). In someexamples, payment terminal 610 is NFC-enabled. FIG. 6C illustrates theuser placing an electronic device 100 into a field 612 of the paymentterminal 610 after the payment terminal requests payment accountinformation. The electronic device 100 incudes a display and one or morewireless communication elements (e.g., one or more wireless antennassuch as NFC antennas, WiFi antennas, etc.) As referenced throughout thisdocument, payment terminal may be an NFC-enabled contactless paymentterminal and field 612 may be an NFC field generated by the contactlesspayment terminal 610.

The electronic device 100 transmits, using the one or more wirelesscommunication elements, payment account information to the paymentterminal 610 that is proximate to the electronic device, wherein thepayment account information enables the payment terminal to engage in apayment transaction. In some embodiments, engaging in the paymenttransaction includes routing information to one or more financialinstitutions to verify payment credentials and/or receive authorizationto complete the transaction. For example, the payment accountinformation is transmitted to a contactless payment terminal using NFC.

Subsequent to engaging in the payment transaction with the paymentterminal, the electronic device receives, from a remote source (e.g.,from the payment terminal via the one or more wireless communicationelements or from a remote server via an Internet connection), loyaltyinformation (e.g., a loyalty number or link to a signup webpage) of aloyalty account (e.g., an existing loyalty account that was used in thepayment transaction or is otherwise associated with the paymenttransaction but is not already associated with the device and was notprovided by the device during the transaction, or a new loyalty accountassociated with a merchant that was a party to the payment transaction).For example, the loyalty information may be received from the paymentterminal or from a server communicatively connected to the paymentterminal.

At FIG. 6D, the device displays, on the display, a linking affordance602 (e.g., for adding the loyalty account to an electronic wallet of theelectronic device).

At FIG. 6E, the device receives user input corresponding to anactivation of the linking affordance 602 (e.g., the user slides thelinking affordance 602 to the right or taps on the linking affordance602). In response to receiving the user input, the electronic devicedisplays, on the display, a user interface 606 for linking the loyaltyaccount to the electronic device.

The user interface 606 may include one or more of: the name of a retailstore associated with the loyalty account (e.g., “Super Market Inc.”), afield 608 for the name of the user, a field 618 for an account number ofthe loyalty account, a field 620 for the address (e.g., mailing oremail) of the user, an option (e.g., affordance 622) to allow the userto specify whether the loyalty account can be automatically providedupon request, a cancel option (e.g., cancellation affordance 604) todecline linking the loyalty account to the electronic device, and an addoption (e.g., confirmation affordance 624) to add the loyalty account tothe electronic device (e.g., to an electronic wallet of the electronicdevice).

In accordance with some embodiments, prior to displaying the linkingaffordance 602, the electronic device determines that the loyaltyaccount is not linked to the electronic device. For example, thisdetermination allows the device to avoid unhelpful notifications (e.g.,don't display the linking affordance 602 when the loyalty account isalready linked to the electronic device).

In accordance with some embodiments, the loyalty information includes anidentifier that is particular to the loyalty account. For example, theloyalty information may include a loyalty account number of the loyaltyaccount or another identifier that corresponds to the loyalty account.

In accordance with some embodiments, the payment transaction is apayment transaction between the payment account and a merchant. The userinterface 606 for linking the loyalty account to the electronic deviceincludes one or more pre-populated fields (e.g., 608, 618, 620, 622).The one or more pre-populated fields are populated with informationassociated with setting up a new loyalty account associated themerchant. In some examples, the content of the fields is pre-populatedusing information available locally at the electronic device, such asthe name, phone number, email, and/or mailing address of the user of theelectronic device. This information may be retrieved, for example, froman electronic phonebook of the electronic device or a database on theelectronic device. In some embodiments, the pre-populated fields includeinformation corresponding to the loyalty account that was provided tothe device after the payment transaction (e.g., a loyalty account numberor name of a merchant associated with the loyalty account) that was,optionally, provided by the merchant or an entity associated with themerchant. Thus, the user can quickly set up a new loyalty account usinguser interface 606.

In accordance with some embodiments, as illustrated in FIG. 6E, the userinterface 606 for linking the loyalty account to the electronic deviceincludes a cancellation affordance 604 (e.g., displayed concurrentlywith the pre-populated fields). The electronic device receives userinput corresponding to an activation of the cancellation affordance 606.In response to receiving the user input corresponding to the activationof the cancellation affordance 606, the electronic device forgoestransmitting content of the one or more pre-populated fields (e.g., 608,618, 620, 622). Thus, if the device detects a user input canceling theloyalty account setup, the user's pre-populated information is nottransmitted to a third-party, and the user's private information is notshared with the third-party unless the user opts into sharing theinformation by joining the loyalty program and/or adding the loyaltycard to their digital wallet.

In accordance with some embodiments, subsequent to activation of thelinking affordance 602, the electronic device receives an inputcorresponding to election of a setting 622 associated with the loyaltyaccount, wherein the setting identifies a status (e.g., a userconfigured preference) for providing loyalty account information of theloyalty account during a subsequent transaction in the absence of input(e.g., user input) specifying a different loyalty account before thedevice receives authorization to proceed with a transaction using thedevice. For example, the user can provide input identifying whether theelectronic device should provide the account information of the loyaltyaccount when a payment terminal requests the information. In someembodiments, the user accepts a pre-selected option for whether theelectronic device should provide the account information of the loyaltyaccount when a payment terminal requests the information.

In accordance with some embodiments, the user interface 606 for linkingthe loyalty account to the electronic device includes a confirmationaffordance 624 to link the loyalty account to the electronic device. Theelectronic device receives activation of the confirmation affordance624, and in response to receiving activation of the confirmationaffordance 624, the electronic device links the loyalty account to theelectronic device. For example, linking the loyalty account to theelectronic device adds the loyalty account to an electronic wallet ofthe electronic device. When the loyalty account is a pre-existingloyalty account, the device can provide a quick technique for linkingthe loyalty account to the electronic device.

FIG. 6F illustrates an exemplary user interface of an electronic walletthat includes a loyalty account that is linked to the electronic device.The user interface of the electronic wallet includes a displayed visualgraphical representation 626 of the loyalty account card associated withthe linked loyalty account. For example, the graphical representationmay include the background image of the physical loyalty account cardassociated with the loyalty account that is distributed to the user bythe associated retail store. Displaying the same background image as thephysical loyalty account card allows the user to easily recognize whichloyalty account is being displayed or accessed.

In some embodiments, prior to receiving the loyalty information (anddisplaying affordance 602), the electronic device receives from thepayment terminal, via the one or more wireless communication elements, arequest for loyalty account information of a first type of loyaltyaccount. For example, at FIG. 6C the payment terminal 610 may requestaccount information for a loyalty account of a particular retail store.In response to receiving the request for the loyalty account informationof the first type of loyalty account, the electronic device transmits tothe payment terminal, via the one or more wireless communicationelements, information indicating that the first type of loyalty accountis not linked to the electronic device. For example, even though a userhas manually keyed in a loyalty account into the payment terminal 610,the payment terminal 610 may use NFC to confirm that the electronicdevice does not already have the appropriate loyalty card linked.

In accordance with some embodiments, the payment transaction isconducted using a payment account of the electronic wallet of theelectronic device (e.g., using payment account information of a paymentaccount linked to the electronic wallet). For example, the paymentaccount was previously linked to the electronic device, as illustratedin FIG. 6F. The electronic wallet of the electronic device may includepayment information (and representations) of a plurality of accounts (inaddition to the linked loyalty account). In FIG. 6F, the electronicwallet includes a visual graphical representation 628 of a Visa creditcard associated with a Visa payment account, a visual graphicalrepresentation 630 of an American Express credit card associated with anAmerican Express payment account, and a visual graphical representation632 of a coffee shop loyalty card associated with a coffee shop loyaltyaccount. The electronic wallet may also include the correspondingpayment account information or loyalty account information for theseaccounts.

In accordance with some embodiments, the electronic wallet of theelectronic device includes payment account information for a secondpayment account associated with a user of the electronic device, whereinthe second payment account is distinct from the payment account.

Although the above description primarily relates to the context ofpayment transactions, a similar technique can be used outside of thecontext of payment transactions. For example, a dedicated loyalty cardterminal that includes an NFC read may push loyalty information to theelectronic device.

FIG. 7 is a flow diagram illustrating a method for linking an account,such as a loyalty account, to an electronic device, in accordance withsome embodiments. Method 700 is performed at a device (e.g., 100, 300,500) with a display and one or more wireless communication elements(e.g., one or more wireless antennas such as NFC antennas, WiFiantennas, etc.). Some operations in method 700 may be combined, theorder of some operations may be changed, and some operations may beomitted.

As described below, method 700 provides an intuitive way for linking anaccount, such as a loyalty account, to an electronic device. The methodreduces the cognitive burden on a user for linking an account to anelectronic device, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user tolink an account to an electronic device faster and more efficientlyconserves power and increases the time between battery charges.

At block 702, the electronic device transmits, using the one or morewireless communication elements, payment account information to apayment terminal (e.g., 610) that is proximate to the electronic device,wherein the payment account information enables the payment terminal(e.g., 610) to engage in a payment transaction. In some embodiments,engaging in the payment transaction includes routing information to oneor more financial institutions to verify payment credentials and/orreceive authorization to complete the transaction. For example, thepayment account information may be transmitted to a contactless paymentterminal (e.g., 610) using NFC.

At block 704, subsequent to engaging in the payment transaction with thepayment terminal (e.g., 610), the electronic device receives, from aremote source (e.g., from the payment terminal via the one or morewireless communication elements or from a remote server via an Internetconnection), loyalty information (e.g., a loyalty number or link to asignup webpage) of a loyalty account (e.g., an existing loyalty accountthat was used in the payment transaction or is otherwise associated withthe payment transaction but is not already associated with the deviceand was not provided by the device during the transaction, or a newloyalty account associated with a merchant that was a party to thepayment transaction). For example, the loyalty information may bereceived from the payment terminal or from a server communicativelyconnected to the payment terminal.

At block 706, the electronic device displays, on the display, a linkingaffordance (e.g., linking affordance 602; for adding the loyalty accountto an electronic wallet of the electronic device).

At block 708, the electronic device receives user input (e.g., a swipeor tap on a touch-sensitive surface of the electronic device)corresponding to an activation of the linking affordance.

At block 710, in response to receiving the user input, the electronicdevice displays, on the display, a user interface (e.g., user interface606) for linking the loyalty account to the electronic device.

In accordance with some embodiments, prior to displaying the linkingaffordance (e.g., 602), the electronic device determines that theloyalty account is not linked to the electronic device.

In accordance with some embodiments, the loyalty information includes anidentifier that is particular to the loyalty account. For example, theloyalty information may include a loyalty account number of the loyaltyaccount or another identifier that corresponds to the loyalty account.

In accordance with some embodiments, the payment transaction is apayment transaction between the payment account and a merchant and theuser interface 606 for linking the loyalty account to the electronicdevice includes one or more pre-populated fields (e.g., 608, 618, 620,622). The one or more pre-populated fields (e.g., 608, 618, 620, 622)are populated with information associated with setting up a new loyaltyaccount associated the merchant. In some examples, the content of thefields (e.g., 608, 620) is pre-populated using information availablelocally at the electronic device, such as the name, phone number, email,and/or mailing address of the user of the device. This information maybe retrieved, for example, from an electronic phonebook of theelectronic device or a database on the electronic device. In someembodiments, the pre-populated fields (e.g., 618) include informationcorresponding to the loyalty account that was provided to the deviceafter the payment transaction (e.g., a loyalty account number or name ofa merchant associated with the loyalty account).

In accordance with some embodiments, the user interface 606 for linkingthe loyalty account to the electronic device includes a cancellationaffordance (e.g., 604; displayed concurrently with the pre-populatedfields). The electronic device receives user input corresponding to anactivation of the cancellation affordance (e.g., 604). In response toreceiving the user input corresponding to the activation of thecancellation affordance (e.g., 604), the electronic device forgoestransmitting content of the one or more pre-populated fields (e.g., 608,618, 620, 622). Thus, if the device detects input canceling the loyaltyaccount setup, the user's pre-populated information is not transmittedto a third-party.

In accordance with some embodiments, the user interface (e.g., 606) forlinking the loyalty account to the electronic device includes aconfirmation affordance (e.g., 624) to link the loyalty account to theelectronic device. The electronic device receives activation of theconfirmation affordance (e.g., 624). In response to receiving activationof the confirmation affordance (e.g., 624), the electronic device linksthe loyalty account to the electronic device. For example, linking theloyalty account to the electronic device adds the loyalty account to anelectronic wallet of the electronic device. When the loyalty account isa pre-existing loyalty account, the device can provide a quick techniquefor linking the loyalty account to the electronic device.

In accordance with some embodiments, subsequent to activation of thelinking affordance (e.g., 602), the electronic device receives an inputcorresponding to election of a setting (e.g., 622) associated with theloyalty account. The setting identifies a status (e.g., a userconfigured preference) for providing loyalty account information of theloyalty account during a subsequent transaction in the absence of inputspecifying a different loyalty account before the device receivesauthorization to proceed with a transaction using the device. Forexample, the user can provide input identifying whether the electronicdevice should provide the account information of the loyalty accountwhen a payment terminal requests the information.

In accordance with some embodiments, prior to receiving the loyaltyinformation, the electronic device receives from the payment terminal(e.g., 610), via the one or more wireless communication elements, arequest for loyalty account information of a first type of loyaltyaccount; (e.g., the payment terminal may request account information fora loyalty account of a particular retail store). In response toreceiving the request for the loyalty account information of the firsttype of loyalty account, the electronic device transmits to the paymentterminal (e.g., 610), via the one or more wireless communicationelements, information indicating that the first type of loyalty accountis not linked to the electronic device. For example, even though a usermanually keys in a loyalty account into the payment terminal (e.g.,610), the payment terminal (e.g., 610) may use NFC to confirm that theelectronic device does not already have the appropriate loyalty cardlinked (e.g., provisioned).

In accordance with some embodiments, the payment transaction wasconducted using a payment account (e.g., represented by 628) of anelectronic wallet of the electronic device. For example, the paymentaccount was previously linked to the electronic device.

In accordance with some embodiments, the electronic wallet includespayment account information for a second payment account (e.g.,represented by 630) associated with a user of the electronic device,wherein the second payment account is distinct from the payment account(e.g., represented by 628).

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7) are also applicable in an analogous manner tothe methods described below. For example, methods 900, 1100, 1300, 1500,1700, and 1900 may include one or more of the characteristics of thevarious methods described above with reference to method 700. Forexample, the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of methods 900, 1100, 1300, 1500, 1700, and 1900optionally have one or more of the characteristics of the electronicwallet, payment accounts, loyalty accounts, affordances, and inputs ofthe electronic device described in method 700. For brevity, thesedetails are not repeated below.

FIGS. 8A-8H illustrate exemplary techniques and exemplary userinterfaces for providing loyalty account information to a paymentterminal, in accordance with some embodiments. For example, a paymentterminal may request loyalty account information for a particularmerchant's loyalty account program. The electronic device uses aloyalty-sharing condition to determine whether to provide the requestedloyalty account information to the payment terminal. The user interfacesin these figures are used to illustrate the processes described below,including the processes in FIG. 9. In some examples, the electronicdevice includes one or more wireless communication elements (e.g., oneor more wireless antennas such as NFC antennas, WiFi antennas, etc.) andone or more input devices (e.g., a touch-sensitive surface).

FIG. 8A illustrates a contactless payment terminal 610 configured toreceive loyalty account information. For example, a user may encountersuch a contactless payment terminal 610 while checking out at asupermarket or other retail store.

In FIG. 8B, the user places the electronic device into a field 612 ofthe contactless payment terminal 610. The electronic device receives,via the one or more wireless communication elements, from thecontactless payment terminal 610 that is proximate to the electronicdevice (e.g., a contactless payment terminal that uses NFC tocommunication with the electronic device), a request for loyalty accountinformation (e.g., loyalty account information of a loyalty account) fora payment transaction for which authorization to proceed has beenprovided (e.g., by a user of the electronic device) via the one or moreinput devices of the electronic device (e.g., a passcode has beenentered on a touchscreen, a physical keyboard, or biometricauthentication has been provided with a biometric sensor such as afingerprint sensor that is embedded in the electronic device).

In response to receiving the request for loyalty account information,the electronic device determines whether a loyalty-sharing condition ismet (e.g., whether the user has pre-authorized the device toautomatically provide loyalty account information for this particularloyalty account at this particular contactless payment terminal). Insome examples, the loyalty-sharing condition is met electronic devicehas previously received an input corresponding to election of a setting(e.g., 622 of FIG. 6E) associated with the loyalty account, wherein thesetting identifies a status (e.g., a user configured preference) toprovide loyalty account information of the loyalty account in theabsence of input (e.g., user input) specifying a different loyaltyaccount before the device receives authorization to proceed with atransaction using the device.

In accordance with a determination that the loyalty-sharing condition ismet (e.g., the user set 622 of FIG. 6E is set to “ON” when linking theloyalty account to the electronic device), the electronic devicetransmits loyalty account information of a loyalty account to thecontactless payment terminal 610 via the one or more wirelesscommunication elements (e.g., the loyalty account information isautomatically transmitted without further input detected by theelectronic device).

In accordance with a determination that the loyalty-sharing condition isnot met (e.g., the user set 622 of FIG. 6E is set to “OFF” when linkingthe loyalty account to the electronic device or is not set at all), theelectronic device forgoes transmitting loyalty account information ofthe loyalty account to the contactless payment terminal.

In accordance with some embodiments, prior to transmitting loyaltyaccount information of the loyalty account, the electronic devicedetermines that authorization to proceed with the payment transaction isprovided, and wherein transmitting loyalty account information of aloyalty account to the contactless payment terminal via the one or morewireless communication elements occurs without requiring separateauthorization. For example, the device determines whether the device hasbeen pre-authorized by the user (e.g., prior to the device receiving therequest from the contactless payment terminal) for proceeding withpayment transactions or whether the user is currently authorizing thedevice to proceed with the payment transaction (e.g., the user hasplaced a finger on a fingerprint sensor for authorization).

As illustrated in FIG. 8C, in accordance with some embodiments, inaccordance with a determination that the loyalty-sharing condition isnot met (e.g., the user set 622 of FIG. 6E is not set) and a loyaltysharing permission regarding user instruction to provide the loyaltyaccount information in the absence of input specifying a differentpayment account before the device receives authorization to proceed witha payment transaction using the device (e.g., automatically) is notstored on the electronic device, the electronic device provides an alert(e.g., a visual, audio, and/or haptic alert; the user interface of FIG.8C) requesting confirmation (e.g., confirmation from the user) toprovide the loyalty account information to the contactless paymentterminal. For example, the user may not have specified whether thedevice should automatically provide the requested loyalty accountinformation. As a result, the device alerts the user via audio, visual,and/or haptic feedback to notify the user that the contactless paymentterminal 610 has requested the loyalty account information.

For example, the user interface of FIG. 8C may include a visualgraphical representation 802 of the loyalty account card associated withthe requested loyalty account, a notification requesting authorization814, an affordance 804, which when activated allows passcodeauthentication input using a keypad, a decline affordance, which whenactivated declines to provide authorization to provide the requestedloyalty account information to the contactless payment terminal 610, anda different visual graphical representation 808 of a second loyaltyaccount.

In accordance with some embodiments, the one or more input devices ofthe electronic device include a fingerprint sensor 816. In accordancewith the determination that the loyalty-sharing condition is not met andwhile detecting a fingerprint on the fingerprint sensor 816 (e.g., theuser has placed the device into the field 612 with their finger on thefingerprint sensor), the electronic device provides a notification(e.g., 814; visual, audio, or haptic alert that the loyalty-sharingcondition is not met) requesting authorization to transmit loyaltyaccount information of the loyalty account to the contactless paymentterminal 610. The electronic device detects, via the one or morewireless communication elements, that the device has been removed from afield 612 of the contactless payment terminal 610 and replaced into thefield 612 of the contactless payment terminal 610. In response todetecting that the device has been replaced into the field 612 of thecontactless payment terminal 610 (and while in the field 610 of thecontactless payment terminal) as illustrated in FIG. 8F, the electronicdevice determines that the fingerprint is consistent with an enrolledfingerprint that is enabled to authorize transactions (e.g., by checkingfor a fingerprint of a user on a fingerprint sensor of the electronicdevice and confirming the fingerprint is authorized for makingtransactions). In response to determining that the fingerprint isconsistent with an enrolled fingerprint that is enabled to authorizetransactions, the electronic device transmits loyalty accountinformation of the loyalty account to the contactless payment terminal610 (e.g., via the one or more wireless communication elements). Thus,the device detects being placed into field 612 with the users finger onthe fingerprint sensor 816, the device alerts the user to authorizeloyalty card use, the device detects being removed the electronic devicefrom field 612, and then the device receives authorization to use theloyalty card by detecting being placed back into the field 612 withoutthe user lifting the finger from the fingerprint sensor 816.

In accordance with some embodiments, the one or more input devices ofthe electronic device include a fingerprint sensor 816. In accordancewith the determination that the loyalty-sharing condition is not met andwhile detecting a fingerprint on the fingerprint sensor 816: theelectronic device provides a notification 814 (e.g., visual, audio,haptic) requesting authorization to transmit loyalty account informationof the loyalty account to the contactless payment terminal 610. Asillustrated in FIG. 8D, the electronic device receives user input (e.g.,detecting activation of graphical representation 808 of a secondaccount; detects that the user shakes or tilts the device) selecting asecond loyalty account (e.g., the account associated with 808) differentfrom the loyalty account. In some examples, as illustrated in FIG. 8E,the electronic device displays confirmation (e.g., displaying graphicalrepresentation 808 of the second account at the top of the display) ofthe user input selecting the second loyalty account. The electronicdevice detects, via the one or more wireless communication elements,that the device has been removed from a field 612 of the contactlesspayment terminal 610 and replaced into the field 612 of the contactlesspayment terminal 610; in response to detecting that the device has beenreplaced into the field 612 of the contactless payment terminal 610 (andwhile in the field of the contactless payment terminal) as illustratedin FIG. 8F, the electronic device determines that the fingerprint isconsistent with an enrolled fingerprint that is enabled to authorizetransactions (e.g., by checking for a fingerprint of a user on afingerprint sensor of the electronic device and confirming thefingerprint is authorized for making transactions); and in response todetermining that the fingerprint is consistent with an enrolledfingerprint that is enabled to authorize transactions, the electronicdevice transmits loyalty account information of the second loyaltyaccount to the contactless payment terminal. Thus, a user places theelectronic device into field 612 with a finger on the fingerprint sensor816, the user receives an alert to authorize loyalty card use, the userremoves the electronic device from field 612, the user switches loyaltycard (e.g., by shaking or tilting device), and then authorizes loyaltycard use by placing the electronic device back into field 612 withoutlifting the finger from fingerprint sensor 816.

In accordance with some embodiments, the one or more input devices ofthe electronic device include a fingerprint sensor 816. In accordancewith the determination that the loyalty-sharing condition is not met andwhile detecting a fingerprint on the fingerprint sensor 816: theelectronic device provides a notification 814 requesting authorizationto transmit loyalty account information of the loyalty account to thecontactless payment terminal (e.g., visual, audio, or haptic alert thatthe loyalty-sharing condition is not met). As illustrated in FIG. 8D,the electronic device receives user input (e.g., detecting activation ofaffordance 806; detecting that the user shakes or tilts the device)declining to use the loyalty account. The electronic device detects, viathe one or more wireless communication elements, that the device hasbeen removed from a field 612 of the contactless payment terminal 610and replaced into the field 612 of the contactless payment terminal 610.In response to detecting that the device has been replaced into thefield 612 of the contactless payment terminal 610 (and while in thefield of the contactless payment terminal) as illustrated in FIG. 8F,the electronic device determines that the fingerprint is consistent withan enrolled fingerprint that is enabled to authorize transactions (e.g.,by checking for a fingerprint of a user on a fingerprint sensor 816 ofthe electronic device and confirming the fingerprint is authorized formaking transactions). In response to determining that the fingerprint isconsistent with an enrolled fingerprint that is enabled to authorizetransactions (and while in the field of the contactless paymentterminal), the electronic device proceeds with the payment transactionwithout transmitting the loyalty account information of the loyaltyaccount to the contactless payment terminal 610 (e.g., transmit anindication to the contactless payment terminal that no loyalty accountinformation will be provided by the electronic device; decline toprovide the loyalty account information of the loyalty account; and/orrequest that the payment transaction proceed without loyalty accountinformation). Thus, the user places the electronic device into field 612with their finger on the fingerprint sensor 816, the user receives analert to authorize loyalty card use, the user removes the electronicdevice from field 612, the user declines to use loyalty card (e.g., byshaking or tilting device), and then authorizes payment (e.g., using adefault payment account) without loyalty (e.g., without using a loyaltyaccount) by placing the electronic device back into field 612 withoutlifting their finger from the fingerprint sensor 816.

In accordance with some embodiments, in accordance with a determinationthat the loyalty-sharing condition is not met and a loyalty sharingpermission stored on the electronic device indicates user instruction tonot provide the loyalty account information in the absence of inputspecifying a different payment account before the device receivesauthorization to proceed with a payment transaction using the device,the electronic device proceeds with the payment transaction using apayment account without prompting for confirmation. For example, theuser has specified that the device should never automatically providethe requested loyalty account information. As a result, the devicemerely proceeds with making a payment using a payment account, such asan account associated with a credit card. The device may indicate to thecontactless payment terminal that the loyalty account information is notavailable. The device may also forgo alerting the user via audio,visual, or haptic feedback that the contactless payment terminal hasrequested the loyalty account information.

In accordance with some embodiments, the loyalty-sharing conditionincludes a condition that is met when the electronic device haspreviously been authorized (e.g., based on user input) to provide theloyalty account information of the loyalty account to the contactlesspayment terminal 610. For example, if this is the first time thisspecific contactless payment terminal 610 is requesting loyalty accountinformation for the loyalty account, then the device requestsauthorization from the user to use the loyalty account at this terminal,but if use of the loyalty account has been authorized at this paymentterminal before, then the device provides the payment informationwithout requesting additional authorization from the user.

In accordance with some embodiments, the loyalty-sharing conditionincludes a condition that is met when the electronic device haspreviously been authorized (e.g., based on user input) to provide theloyalty account information of the loyalty account to a differentcontactless payment terminal in a group of contactless payment terminalsthat includes the contactless payment terminal 610. For example, if thisis the first time a contactless payment terminal at a particular branchof a retail store is requesting loyalty account information for theloyalty account, then the device requests authorization from the user touse the loyalty account at this terminal, but if use of the loyaltyaccount has been authorized at this payment terminal before, then thedevice provides the payment information without requesting additionalauthorization from the user.

In accordance with some embodiments, the loyalty-sharing conditionincludes a condition that is met when the electronic device haspreviously been authorized (e.g., based on user input) to provide theloyalty account information of the loyalty account to one or morecontactless payment terminals within a predetermined geographical regionin which the contactless payment terminal is located. For example, ifthis is the first time a contactless payment terminal is requestingloyalty account information for the loyalty account while the device isin a predetermined geographic region (e.g., a store, city, or state),then the device requests authorization from the user to use the loyaltyaccount at this terminal, but if use of the loyalty account has beenpreviously authorization in the predetermined region, then the deviceprovides the payment information without requesting additionalauthorization from the user.

In accordance with some embodiments, prior to receiving the request forloyalty account information, the electronic device detects a field(e.g., an NFC field) of the contactless payment terminal, and prior todetecting the field of the contactless payment terminal, the electronicdevice receives, via the one or more input devices of the electronicdevice, the authorization to proceed (e.g., user pre-arms the device forpayment before reaching the contactless payment terminal 610).

In accordance with some embodiments, prior to receiving the request forloyalty account information, the electronic device detects a field(e.g., an NFC field) of the contactless payment terminal; and whiledetecting the field of the contactless payment terminal, the electronicdevice receives, via the one or more input devices of the electronicdevice, the authorization to proceed (e.g., user arms the device forpayment while at the contactless payment terminal 610).

In accordance with some embodiments, after transmitting loyalty accountinformation of a loyalty account to the contactless payment terminal viathe one or more wireless communication elements for a predefined numberof loyalty accounts, the electronic device receives a request forloyalty account information of a second loyalty account (e.g.,associated with 808) from the contactless payment terminal 610. Inresponse to receiving the request for loyalty account information of thesecond loyalty account from the contactless payment terminal 610, theelectronic device forgoes transmitting loyalty account information ofthe second loyalty account to the contactless payment terminal 610 forthe payment transaction. For example, the contactless payment terminal610 may request loyalty account information for multiple loyaltyaccounts. The electronic device may refuse to provide the loyaltyaccount information for more than a predefined number of loyaltyaccounts during a single payment transaction. This helps prevent acontactless payment terminal from collecting information about theloyalty accounts provisioned on the electronic device. In someembodiments, there is a temporal threshold that is considered by thedevice when responding to requests for loyalty information (e.g., onlythe predefined number of loyalty account information requests areresponded to within a predetermined amount of time, such as 5 minutes).

In accordance with some embodiments, the one or more input devicescomprises a fingerprint sensor 816 and the authorization was provided inaccordance with: detecting a respective fingerprint on the fingerprintsensor of the electronic device; and in response to detecting therespective fingerprint on the fingerprint sensor, determining that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize payment transactions.

In accordance with some embodiments, the one or more input devicescomprises a touch-sensitive surface and wherein the authorization wasprovided in accordance with: receiving a passcode via thetouch-sensitive surface of the electronic device; and in response toreceiving the passcode, determining that the passcode is consistent withan enrolled passcode that is enabled to authorize payment transactions.In some embodiments, authorization to provide loyalty accountinformation includes interaction with a notification displayed on adisplay of the device (e.g., receiving user selection of “ok” on a popup notification that states “do you want to use loyalty card X for thistransaction?”).

In accordance with some embodiments, the payment transaction isconducted using a payment account of an electronic wallet of theelectronic device. For example, the payment account was previouslylinked to the electronic device.

In accordance with some embodiments, an electronic wallet of theelectronic device includes loyalty account information for one or moredifferent loyalty accounts associated with a user of the electronicdevice, the one or more different loyalty accounts being different fromthe loyalty account used for the payment transaction.

As illustrated in FIG. 8F, a user places the electronic device into afield 612 of a contactless payment terminal 610. In accordance with someembodiments, the electronic device transmits, using the one or morewireless communication elements, payment account information to thecontactless payment terminal, wherein the payment account informationenables the contactless payment terminal to engage in the paymenttransaction. In some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction. For example, the payment account information may betransmitted to a contactless payment terminal using NFC.

As illustrated in FIG. 8G, in some embodiments, after transmittingloyalty account information and payment account information to thecontactless payment terminal 610, the electronic device displays avisual graphical representation 802 of the loyalty account used in thepayment transaction and the a visual graphical representation 810 of thepayment account used in the payment transaction.

As illustrated in FIG. 8G, in some embodiments, before transmittingloyalty account information and payment account information to thecontactless payment terminal 610, the electronic device displays avisual graphical representation 802 of the loyalty account to be used inthe payment transaction and the a visual graphical representation 810 ofthe payment account to be used in the payment transaction.

FIG. 9 is a flow diagram illustrating a method for providing loyaltyaccount information to a payment terminal, in accordance with someembodiments. Method 900 is performed at a device (e.g., 100, 300, 500)with one or more wireless communication elements (e.g., one or morewireless antennas such as NFC antennas, WiFi antennas, etc.) and one ormore input devices (e.g., touch-sensitive surface, fingerprint sensor).Some operations in method 900 may be combined, the order of someoperations may be changed, and some operations may be omitted.

As described below, method 900 provides an intuitive way for providingloyalty account information to a payment terminal, in accordance withsome embodiments. The method reduces the cognitive burden on a user forlinking an account to an electronic device, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to link an account to an electronic devicefaster and more efficiently conserves power and increases the timebetween battery charges.

At block 902, the electronic device receives, via the one or morewireless communication elements, from a contactless payment terminal(e.g., 610) that is proximate to the electronic device (e.g., acontactless payment terminal that uses NFC to communication with theelectronic device), a request for loyalty account information (e.g.,loyalty account information of a loyalty account) for a paymenttransaction for which authorization to proceed has been provided (e.g.,by a user of the electronic device) via the one or more input devices ofthe electronic device (e.g., a passcode has been entered on atouchscreen, a physical keyboard, or biometric authentication has beenprovided with a biometric sensor such as a fingerprint sensor that isembedded in the electronic device).

At block 904, in response to receiving the request for loyalty accountinformation, blocks 906-910 are performed.

At block 906, the electronic device determines whether a loyalty-sharingcondition is met (e.g., whether the user has pre-authorized the deviceto automatically provide loyalty account information for this particularloyalty account at this particular contactless payment terminal).

At block 908, in accordance with a determination that theloyalty-sharing condition is met, the electronic device transmitsloyalty account information of a loyalty account to the contactlesspayment terminal 610 via the one or more wireless communication elements(e.g., the loyalty account information is automatically transmittedwithout further input detected by the electronic device).

At block 910, in accordance with a determination that theloyalty-sharing condition is not met, the electronic device forgoestransmitting loyalty account information of the loyalty account to thecontactless payment terminal 610.

In accordance with some embodiments, prior to transmitting loyaltyaccount information of the loyalty account, the electronic devicedetermines that authorization to proceed with the payment transaction isprovided, and wherein transmitting loyalty account information of aloyalty account to the contactless payment terminal via the one or morewireless communication elements occurs without requiring separateauthorization. For example, the device determines whether the device hasbeen pre-authorized by the user (e.g., prior to the device receiving therequest from the contactless payment terminal) for proceeding withpayment transactions or whether the user is currently authorizing thedevice to proceed with the payment transaction (e.g., the user hasplaced a finger on a fingerprint sensor for authorization).

In some embodiments, in accordance with a determination that theloyalty-sharing condition is not met and a loyalty sharing permissionregarding user instruction to provide the loyalty account information inthe absence of input specifying a different payment account before thedevice receives authorization to proceed with a payment transactionusing the device (e.g., automatically) is not stored on the electronicdevice, the electronic device provides an alert (e.g., a visual, audio,and/or haptic alert; the user interface of FIG. 8C) requestingconfirmation (e.g., confirmation from the user) to provide the loyaltyaccount information to the contactless payment terminal.

In accordance with some embodiments, the one or more input devices ofthe electronic device include a fingerprint sensor (e.g., 816). Inaccordance with the determination that the loyalty-sharing condition isnot met and while detecting a fingerprint on the fingerprint sensor(e.g., 816), the electronic device provides a notification (e.g., 814)requesting authorization to transmit loyalty account information of theloyalty account to the contactless payment terminal (e.g., 610). Theelectronic device detects, via the one or more wireless communicationelements, that the device has been removed from a field (e.g., 612) ofthe contactless payment terminal (e.g., 610) and replaced into the field(e.g., 612) of the contactless payment terminal (e.g., 610). Forexample, the user removes the device from the field (e.g., 612) to viewthe notification provided by the electronic device. In response todetecting that the device has been replaced into the field (e.g., 612)of the contactless payment terminal (e.g., 610), the electronic devicedetermines that the fingerprint is consistent with an enrolledfingerprint that is enabled to authorize transactions. In response todetermining that the fingerprint is consistent with an enrolledfingerprint that is enabled to authorize transactions, the electronicdevice transmits loyalty account information of the loyalty account tothe contactless payment terminal (e.g., 610). Thus, the electronicdevice detects field (e.g., 612) while a user's finger is on thefingerprint sensor (e.g., 816), the device alerts the user requestingauthorization to use the loyalty card. The device detects being removedfrom the field (e.g., 612), and then detects being placed back intofield (e.g., 612) while the user's finger continues to be on thefingerprint sensor (e.g., 816).

In accordance with some embodiments, the one or more input devices ofthe electronic device include a fingerprint sensor (e.g., 816). Inaccordance with the determination that the loyalty-sharing condition isnot met and while detecting a fingerprint on the fingerprint sensor(e.g., 816), the electronic device provides a notification (e.g., 814)requesting authorization to transmit loyalty account information of theloyalty account to the contactless payment terminal (e.g., 610). Theelectronic device receives user input selecting a second loyalty account(e.g., the account associated with 808) different from the loyaltyaccount. In some examples, as illustrated in FIG. 8E, the electronicdevice displays confirmation (e.g., displaying graphical representation808 of the second account at the top of the display) of the user inputselecting the second loyalty account. The electronic device detects, viathe one or more wireless communication elements, that the device hasbeen removed from a field (e.g., 612) of the contactless paymentterminal (e.g., 610) and replaced into the field (e.g., 612) of thecontactless payment terminal (e.g., 610). For example, the user removesthe device from the field (e.g., 612) to provide input selecting thesecond loyalty account. In response to detecting that the device hasbeen replaced into the field (e.g., 612) of the contactless paymentterminal (e.g., 610), the electronic device determines that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize transactions. In response to determining that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize transactions, the electronic device transmits loyaltyaccount information of the second loyalty account to the contactlesspayment terminal.

In accordance with some embodiments, the one or more input devices ofthe electronic device include a fingerprint sensor (e.g., 816). Inaccordance with the determination that the loyalty-sharing condition isnot met and while detecting a fingerprint on the fingerprint sensor(e.g., 816), the electronic device provides a notification (e.g., 814)requesting authorization to transmit loyalty account information of theloyalty account to the contactless payment terminal. The electronicdevice receives user input declining (e.g., detecting activation ofaffordance 806) to use the loyalty account. The electronic devicedetects, via the one or more wireless communication elements, that thedevice has been removed from a field (e.g., 612) of the contactlesspayment terminal (e.g., 610) and replaced into the field (e.g., 612) ofthe contactless payment terminal (e.g., 610). For example, the userremoves the device from the field (e.g., 612) to provide input decliningto use the loyalty account. In response to detecting that the device hasbeen replaced into the field (e.g., 612) of the contactless paymentterminal (e.g., 610), the electronic device determines that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize transactions. In response to determining that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize transactions, the electronic device proceeds with thepayment transaction without transmitting the loyalty account informationof the loyalty account to the contactless payment terminal (e.g., 610).

In accordance with some embodiments, in accordance with a determinationthat the loyalty-sharing condition is not met and a loyalty sharingpermission stored on the electronic device indicates user instruction tonot provide the loyalty account information in the absence of inputspecifying a different payment account before the device receivesauthorization to proceed with a payment transaction using the device,the electronic device proceeds with the payment transaction using apayment account without prompting for confirmation.

In accordance with some embodiments, the loyalty-sharing conditionincludes a condition that is met when the electronic device haspreviously been authorized to provide the loyalty account information ofthe loyalty account to the contactless payment terminal (e.g., 610). Forexample, the device may receive user input indicating that the loyaltyaccount information of the loyalty account can be provided to anycontactless payment terminal that requests the information, tocontactless payment terminals of a particular merchant, or tocontactless payment terminals at a particular location (e.g., apredefined geographical location).

In accordance with some embodiments, the loyalty-sharing conditionincludes a condition that is met when the electronic device haspreviously been authorized to provide the loyalty account information ofthe loyalty account to a different contactless payment terminal in agroup of contactless payment terminals that includes the contactlesspayment terminal (e.g., 610). For example, the device receives userinput indicating that the loyalty account information of the loyaltyaccount can be provided to a first payment terminal of a merchant. As aresult of receiving the user input, the loyalty-sharing condition is metfor all other payment terminals of the same merchant. For anotherexample, the device receives user input indicating that the loyaltyaccount information of the loyalty account can be provided to a paymentterminal of a gas station (e.g., merchant type). As a result ofreceiving the user input, the loyalty-sharing condition is met for allother payment terminals of gas stations (e.g., of the same merchanttype).

In accordance with some embodiments, the loyalty-sharing conditionincludes a condition that is met when the electronic device haspreviously been authorized to provide the loyalty account information ofthe loyalty account to one or more contactless payment terminals withina predetermined geographical region in which the contactless paymentterminal is located. For example, the device receives user inputindicating that the loyalty account information of the loyalty accountcan be provided to a first payment terminal that is located at amerchant's retail store (e.g., a predetermined geographical region). Asa results of receiving the user input, the loyalty sharing condition ismet a second payment terminal that is located at the merchant's sameretail store (e.g., the predetermined geographical region).

In accordance with some embodiments, prior to receiving the request forloyalty account information, the electronic device detects a field(e.g., 612) of the contactless payment terminal (e.g., 612), and priorto detecting the field (e.g., 612) of the contactless payment terminal(e.g., 610), the electronic device receives, via the one or more inputdevices of the electronic device, the authorization to proceed.

In accordance with some embodiments, prior to receiving the request forloyalty account information, the electronic device detects a field(e.g., 612) of the contactless payment terminal (e.g., 610); and whiledetecting the field (e.g., 612) of the contactless payment terminal(e.g., 610), the electronic device receives, via the one or more inputdevices of the electronic device, the authorization to proceed.

In accordance with some embodiments, after transmitting loyalty accountinformation of a loyalty account to the contactless payment terminal viathe one or more wireless communication elements for a predefined numberof loyalty accounts, the electronic device receives a request forloyalty account information of a second loyalty account from thecontactless payment terminal (e.g., 610). In response to receiving therequest for loyalty account information of the second loyalty accountfrom the contactless payment terminal (e.g., 610), the electronic deviceforgoes transmitting loyalty account information of the second loyaltyaccount to the contactless payment (e.g., 610) for the paymenttransaction.

In accordance with some embodiments, the one or more input devicescomprises a fingerprint sensor (e.g., 816) and the authorization wasprovided in accordance with: detecting a respective fingerprint on thefingerprint sensor (e.g., 816) of the electronic device; and in responseto detecting the respective fingerprint on the fingerprint sensor (e.g.,816), determining that the fingerprint is consistent with an enrolledfingerprint that is enabled to authorize payment transactions.

In accordance with some embodiments, the one or more input devicescomprises a touch-sensitive surface and wherein the authorization wasprovided in accordance with: receiving a passcode via thetouch-sensitive surface of the electronic device; and in response toreceiving the passcode, determining that the passcode is consistent withan enrolled passcode that is enabled to authorize payment transactions.

In accordance with some embodiments, the payment transaction isconducted using a payment account of an electronic wallet of theelectronic device.

In accordance with some embodiments, an electronic wallet of theelectronic device includes loyalty account information for one or moredifferent loyalty accounts associated with a user of the electronicdevice, the one or more different loyalty accounts being different fromthe loyalty account used for the payment transaction.

At block 912, in accordance with some embodiments, the electronic devicetransmits, using the one or more wireless communication elements,payment account information to the contactless payment terminal (e.g.,610), wherein the payment account information enables the contactlesspayment terminal (e.g., 610) to engage in the payment transaction.

In some embodiments, after transmitting loyalty account information andpayment account information to the contactless payment terminal (e.g.,610), as illustrated in FIG. 8H, the electronic device displays a visualgraphical representation (e.g., 822) of the loyalty account used in thepayment transaction and the a visual graphical representation (e.g.,824) of the payment account used in the payment transaction. Forexample, the user interface also includes the name of the merchant(“Super Market Inc.”) that processed the transaction, the total amount(“$126.24”) of the transaction, the date (“Today”) or time (“3:06 pm” ofthe transaction, an amount saved (“$14.33”) as a result of using theloyalty account, and one or more previous transactions (e.g., 826)associated with the payment card.

In some embodiments, before transmitting loyalty account information andpayment account information to the contactless payment terminal (e.g.,610), the electronic device displays a visual graphical representation(e.g., 802) of the loyalty account to be used in the payment transactionand the a visual graphical representation (e.g., 810) of the paymentaccount to be used in the payment transaction.

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9) are also applicable in an analogous manner tothe methods described above and below. For example, methods 700, 900,1100, 1300, 1500, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 900. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 1100, 1300,1500, 1700, and 1900 optionally have one or more of the characteristicsof the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method900. For brevity, these details are not repeated below.

FIGS. 10A-10C illustrate exemplary techniques and exemplary userinterfaces for displaying indications of payment accounts and loyaltyaccounts for a payment transaction, in accordance with some embodiments.For example, an electronic device 100 with one or more wirelesscommunication elements (e.g., one or more wireless antennas such as NFCantennas, WiFi antennas, etc.) and a display is used by the technique.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIG. 11.

At FIG. 10A, a user places the electronic device 100 into a field 612 ofa contactless payment terminal. The electronic device receives, via theone or more wireless communication elements, information about a paymenttransaction for which a loyalty account is available to be used (e.g.,detecting a field of a contactless payment terminal and determining thatthe device is in a location in which the loyalty account can be used;receiving information from the contactless payment terminal that loyaltyaccount information has been entered at the payment transactionterminal; or receiving information from the contactless payment terminalthat the loyalty account, if available, would be accepted).

At FIG. 10B, in response to receiving the information about the paymenttransaction, the electronic device concurrently displays, on thedisplay: an indication 1004 of a payment account for the paymenttransaction and an indication 1002 of the loyalty account for thepayment transaction.

In accordance with some embodiments, subsequent to the electronic deviceconcurrently displaying, on the display, the indication 1004 of thepayment account for the payment transaction and the indication 1002 ofthe loyalty account for the payment transaction, the electronic deviceconducts the payment transaction using the payment account of anelectronic wallet of the electronic device. For example, the paymentaccount was previously linked to the electronic device and theelectronic device provides payment account information to thecontactless payment terminal 610 for conducting the payment transaction.Thus, the indication 1004 of the payment account and the indication 1002of the loyalty account are at least displayed prior to conducting thepayment transaction.

In accordance with some embodiments, prior to the electronic deviceconcurrently displaying, on the display, the indication 1004 of thepayment account for the payment transaction and the indication 1002 ofthe loyalty account for the payment transaction, the electronic deviceconducts the payment transaction using the payment account of anelectronic wallet of the electronic device. For example, the paymentaccount was previously linked to the electronic device and theelectronic device provides payment account information to thecontactless payment terminal 610 for conducting the payment transaction.Thus, the indication 1004 of the payment account and the indication 1002of the loyalty account are at least displayed subsequent to conductingthe payment transaction.

In accordance with some embodiments, prior to the electronic devicereceiving, via the one or more wireless communication elements,information about the payment transaction for which a loyalty account isavailable: the electronic device detects a field 612 of the contactlesspayment terminal 610 and the electronic device determines that theelectronic device is in a location in which the loyalty account can beused.

In accordance with some embodiments, prior to the electronic devicereceiving, via the one or more wireless communication elements,information about the payment transaction for which a loyalty account isavailable: the electronic device receives, via the one or more wirelesscommunication elements, information from the contactless paymentterminal 610 indicating that loyalty account information has beenentered at the payment transaction terminal (e.g., manually entered bythe user entering a phone number).

In accordance with some embodiments, prior to the electronic devicereceiving, via the one or more wireless communication elements,information about the payment transaction for which a loyalty account isavailable: the electronic device receives, via the one or more wirelesscommunication elements, information from the contactless paymentterminal 610 indicating that the loyalty account would be accepted(e.g., if the loyalty account were made available to the contactlesspayment terminal).

In accordance with some embodiments, the payment transaction isconducted using a payment account of an electronic wallet of theelectronic device. For example, the payment account was previouslylinked to the electronic device.

In accordance with some embodiments, an electronic wallet of theelectronic device includes loyalty account information for one or moredifferent loyalty accounts associated with a user of the electronicdevice, the one or more different loyalty accounts being different fromthe loyalty account used for the payment transaction.

In accordance with some embodiments, an electronic wallet of theelectronic device includes loyalty account information for the loyaltyaccount and payment account information for the payment account.

In accordance with some embodiments, the payment account is a defaultpayment account.

In accordance with some embodiments, concurrently displaying, on thedisplay, the indication 1004 of the payment account for the paymenttransaction and the indication 1002 of the loyalty account for thepayment transaction occurs prior to receiving authorization to proceedwith the payment transaction (e.g., as a proposed loyalty account foruse in the payment transaction). Authorization to proceed may comprisedetecting a respective fingerprint on a fingerprint sensor 1018 of theelectronic device, wherein the respective fingerprint is determined tobe consistent with an enrolled fingerprint that is enabled to authorizepayment transactions. For example, the device receives authentication bymatching information from the detected fingerprint to information fromknown fingerprints to confirm that the user is an authorized user.Authorization to proceed may comprise receiving a passcode via atouch-sensitive surface of the electronic device, the passcode beingdetermined to be consistent with an enrolled passcode that is enabled toauthorize payment transactions.

In accordance with some embodiments, the electronic device transmits,using the one or more wireless communication elements, payment accountinformation of the payment account to the contactless payment terminal610, wherein the payment account information enables the contactlesspayment terminal to engage in the payment transaction. In someembodiments, engaging in the payment transaction includes routinginformation to one or more financial institutions to verify paymentcredentials and/or receive authorization to complete the transaction.For example, the payment account information may be transmitted to thecontactless payment terminal using NFC.

In accordance with some embodiments, subsequent to transmitting paymentaccount information of the payment account, the electronic devicetransmits, using the one or more wireless communication elements,loyalty account information of the loyalty account to the contactlesspayment terminal 610 (e.g., in response to a request for loyaltyinformation that is received from the contactless payment terminal 610after the payment account information is provided to the contactlesspayment terminal 610).

In accordance with some embodiments, prior to the electronic devicetransmitting payment account information of the payment account, theelectronic device transmits, using the one or more wirelesscommunication elements, loyalty account information of the loyaltyaccount to the contactless payment terminal 610 (e.g., in response to arequest for loyalty information that is received from the contactlesspayment terminal 610 before the payment account information is providedto the contactless payment terminal 610).

In accordance with some embodiments, the electronic device receives(e.g., from the contactless payment terminal 610), using the one or morewireless communication elements, confirmation of acceptance of paymentaccount information of the payment account and loyalty accountinformation of the loyalty account. As illustrated in FIG. 10C, inresponse to receiving confirmation of acceptance of payment accountinformation, the electronic device displays, on the display, aconfirmation of acceptance of payment account information of the paymentaccount and loyalty account information of the loyalty account (e.g.,1008, 1010, 1014).

In accordance with some embodiments, the electronic device determinesthat the contactless payment terminal has not approved the loyaltyaccount. In response to determining that the contactless paymentterminal has not approved the loyalty account, the electronic devicedisplays the indication of the payment account and the electronic deviceforgoes display of the indication of the loyalty account.

In accordance with some embodiments, prior to transmitting the paymentaccount to the contactless payment terminal 610, the electronic devicedisplays, on the display, a description of a prospective benefit (e.g.,10% off purchases, 2× gas points) of using a loyalty program associatedwith the loyalty account.

In accordance with some embodiments, as illustrated in FIG. 10C,subsequent to transmitting the payment account to the contactlesspayment terminal, the electronic device displays, on the display, adescription 1012 of savings generated (e.g., “$20 dollars saved”) byusing a loyalty program associated with the loyalty account.

In accordance with some embodiments, subsequent to the electronic devicetransmitting the payment account to the contactless payment terminal,the electronic device displays, on the display, an indication ofprogress toward an objective (e.g., “You have bought X sandwiches. Ifyou buy Y sandwiches, your next sandwich is free!”) associated with theloyalty account. The indication may be displayed prior to completing thepayment transaction, subsequent to completing the payment transaction,or both prior to and subsequent to completing the payment transaction.

In some embodiments, the electronic device displays (e.g., in a paymenthistory log) an amount paid 1010. The amount paid is received via NFCfrom the contactless payment terminal at the time of the paymenttransaction. In some embodiments, the electronic device displays (e.g.,in a payment history log) an amount saved 1102 and a representation ofthe loyalty account. The amount saved is received via NFC from thecontactless payment terminal at time of transaction. In someembodiments, the amount saved is received via the Internet, subsequentto completion of the payment transaction. In some embodiments, theelectronic device displays a date/time of a particular transaction andthe name of the retailer (e.g., merchant) that processed thetransaction.

FIG. 11 is a flow diagram illustrating a method for displayingindications of payment accounts and loyalty accounts for a paymenttransaction, in accordance with some embodiments. Method 1100 isperformed at a device (e.g., 100, 300, 500) with one or more wirelesscommunication elements (e.g., one or more wireless antennas such as NFCantennas, WiFi antennas, etc.) and a display. Some operations in method1100 may be combined, the order of some operations may be changed, andsome operations may be omitted.

As described below, method 1100 provides an intuitive way for displayingindications of payment accounts and loyalty accounts for a paymenttransaction, in accordance with some embodiments. The method reduces thecognitive burden on a user for displaying indications of paymentaccounts and loyalty accounts for a payment transaction, therebycreating a more efficient human-machine interface. For battery-operatedcomputing devices, displaying indications of payment accounts andloyalty accounts for a payment transaction faster and more efficientlyconserves power and increases the time between battery charges.

At block 1102, the electronic device receives, via the one or morewireless communication elements, information about a payment transactionfor which a loyalty account is available to be used (e.g., detecting afield of a contactless payment terminal and determining that the deviceis in a location in which the loyalty account can be used; receivinginformation from the contactless payment terminal that loyalty accountinformation has been entered at the payment transaction terminal; orreceiving information from the contactless payment terminal that theloyalty account, if available, would be accepted).

At block 1104, in response to receiving the information about thepayment transaction, the electronic device concurrently displays, on thedisplay: an indication (e.g., 1004) of a payment account for the paymenttransaction and an indication (e.g., 1002) of the loyalty account forthe payment transaction.

At block 1106, in accordance with some embodiments, subsequent toconcurrently displaying, on the display, the indication of the paymentaccount for the payment transaction and the indication of the loyaltyaccount for the payment transaction, the electronic device conducts thepayment transaction using the payment account of an electronic wallet ofthe electronic device.

In accordance with some embodiments, prior to concurrently displaying,on the display, the indication (e.g., 1004) of the payment account forthe payment transaction and the indication (e.g., 1002) of the loyaltyaccount for the payment transaction, the electronic device conducts thepayment transaction using the payment account of an electronic wallet ofthe electronic device.

In accordance with some embodiments, prior to the electronic devicereceiving, via the one or more wireless communication elements,information about the payment transaction for which a loyalty account isavailable: the electronic device detects a field (e.g., 612) of thecontactless payment terminal (e.g., 610) and the electronic devicedetermines that the electronic device is in a location in which theloyalty account can be used.

In accordance with some embodiments, prior to the electronic devicereceiving, via the one or more wireless communication elements,information about the payment transaction for which a loyalty account isavailable: the electronic device receives, via the one or more wirelesscommunication elements, information from the contactless paymentterminal (e.g., 610) indicating that loyalty account information hasbeen entered at the payment transaction terminal.

In accordance with some embodiments, prior to the electronic devicereceiving, via the one or more wireless communication elements,information about the payment transaction for which a loyalty account isavailable: the electronic device receives, via the one or more wirelesscommunication elements, information from the contactless paymentterminal (e.g., 610) indicating that the loyalty account would beaccepted.

In accordance with some embodiments, the payment transaction isconducted using a payment account of an electronic wallet of theelectronic device.

In accordance with some embodiments, an electronic wallet of theelectronic device includes loyalty account information for one or moredifferent loyalty accounts associated with a user of the electronicdevice, the one or more different loyalty accounts being different fromthe loyalty account used for the payment transaction.

In accordance with some embodiments, an electronic wallet of theelectronic device includes loyalty account information for the loyaltyaccount and payment account information for the payment account.

In accordance with some embodiments, the payment account is a defaultpayment account.

In accordance with some embodiments, concurrently displaying, on thedisplay, the indication (e.g., 1004) of the payment account for thepayment transaction and the indication (e.g., 1002) of the loyaltyaccount for the payment transaction occurs prior to receivingauthorization to proceed with the payment transaction. Authorization toproceed may comprise detecting a respective fingerprint on a fingerprintsensor (e.g., 1018) of the electronic device, wherein the respectivefingerprint is determined to be consistent with an enrolled fingerprintthat is enabled to authorize payment transactions. Authorization toproceed may comprise receiving a passcode via a touch-sensitive surfaceof the electronic device, the passcode being determined to be consistentwith an enrolled passcode that is enabled to authorize paymenttransactions.

In accordance with some embodiments, the electronic device transmits,using the one or more wireless communication elements, payment accountinformation of the payment account to the contactless payment terminal(e.g., 610), wherein the payment account information enables thecontactless payment terminal to engage in the payment transaction. Insome embodiments, engaging in the payment transaction includes routinginformation to one or more financial institutions to verify paymentcredentials and/or receive authorization to complete the transaction.

In accordance with some embodiments, subsequent to transmitting paymentaccount information of the payment account, the electronic devicetransmits, using the one or more wireless communication elements,loyalty account information of the loyalty account to the contactlesspayment terminal (e.g., 610).

In accordance with some embodiments, prior to the electronic devicetransmitting payment account information of the payment account, theelectronic device transmits, using the one or more wirelesscommunication elements, loyalty account information of the loyaltyaccount to the contactless payment terminal (e.g., 610).

In accordance with some embodiments, the electronic device receives(e.g., from the contactless payment terminal 610), using the one or morewireless communication elements, confirmation of acceptance of paymentaccount information of the payment account and loyalty accountinformation of the loyalty account. In response to receivingconfirmation of acceptance of payment account information, theelectronic device displays, on the display, a confirmation of acceptanceof payment account information of the payment account and loyaltyaccount information of the loyalty account (e.g., 1008, 1010, 1014).

In accordance with some embodiments, the electronic device determinesthat the contactless payment terminal has not approved the loyaltyaccount. In response to determining that the contactless paymentterminal has not approved the loyalty account, the electronic devicedisplays the indication of the payment account and the electronic deviceforgoes display of the indication of the loyalty account.

In accordance with some embodiments, prior to transmitting the paymentaccount to the contactless payment terminal 610, the electronic devicedisplays, on the display, a description of a prospective benefit ofusing a loyalty program associated with the loyalty account.

In accordance with some embodiments, subsequent to transmitting thepayment account to the contactless payment terminal, the electronicdevice displays, on the display, a description 1012 of savings generatedby using a loyalty program associated with the loyalty account.

In accordance with some embodiments, subsequent to the electronic devicetransmitting the payment account to the contactless payment terminal,the electronic device displays, on the display, an indication ofprogress toward an objective associated with the loyalty account. Theindication may be displayed prior to completing the payment transaction,subsequent to completing the payment transaction, or both prior to andsubsequent to completing the payment transaction.

In some embodiments, the electronic device displays (e.g., in a paymenthistory log) an amount paid (e.g., 1010). The amount paid is receivedvia NFC from the contactless payment terminal at the time of the paymenttransaction. In some embodiments, the electronic device displays (e.g.,in a payment history log) an amount saved (e.g., 1102) and arepresentation of the loyalty account. The amount saved is received viaNFC from the contactless payment terminal at time of transaction. Insome embodiments, the amount saved is received via the Internet,subsequent to completion of the payment transaction. In someembodiments, the electronic device displays a date/time of a particulartransaction and the name of the retailer (e.g., merchant) that processedthe transaction.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIG. 11) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1300, 1500, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1100. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1300,1500, 1700, and 1900 optionally have one or more of the characteristicsof the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1100. For brevity, these details are not repeated below.

FIGS. 12A-12E illustrate exemplary techniques and exemplary userinterfaces for proceeding with a payment transaction using a paymentaccount of a requested payment account type, in accordance with someembodiments. For example, an electronic device 100 with one or morewireless communication elements (e.g., one or more wireless antennassuch as NFC antennas, WiFi antennas, etc.) is used by the technique. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 13.

A merchant may have a preference for a private label payment account (ascompared to a regular payment account) that is offered to customers' ofthe merchant. Thus, the payment terminals of the merchant may beconfigured to request (e.g., from an electronic device) payment in theform of the private label payment account during a payment transaction,such as during a payment transaction using an NFC-enabled paymentterminal and an NFC-enabled electronic device. For example, the paymentterminals may request that payment be made using a particular type ofpayment account.

However, payment account information is generally not shared by theelectronic device without the user's permission, even if a paymentterminal requests the information. For example, the permission may beprovided in advance, such as through an indication that payments may bemade using a particular private label account at particular terminals orlocations. For another example, the permission may be provided at thetime of the transaction, such as by confirming that a requested privatelabel account may be used (rather than a default payment account) in thepayment transaction.

At FIG. 12A, a user places the electronic device 100 into a field 612 ofcontactless payment terminal 610. For example, the contactless paymentterminal 610 is NFC-enabled and the field 612 is an NFC field. Theelectronic device receives, from the contactless payment terminal 610(e.g., a contactless payment terminal that uses NFC to communicationwith the electronic device) via the one or more wireless communicationelements, a request (e.g., for payment account information of a paymentaccount or loyalty account information of a loyalty account) associatedwith a payment transaction.

The electronic device determines whether the request comprises a requestfor payment using a particular payment account type (e.g., a particularretailer's private label credit card). In accordance with adetermination that the request does not comprise the request for paymentusing the particular payment account type, proceeding with the paymenttransaction using a default payment account (e.g., transmitting anidentifier, such as a PAN (“Primary Account Number”), of the requestedparticular payment account to the contactless payment terminal). Thus,when a payment terminal does not ask for a particular payment account,the electronic device may proceed with the payment transaction byproviding account information for the default payment account. Asillustrated in FIG. 12B, in some embodiments, the electronic devicedisplays an indication 1202 of the default payment account to notify theuser that the default payment account will be used in the paymenttransaction.

In accordance with a determination that the request comprises therequest for payment using the particular payment account type (e.g.,contactless payment terminal requests a particular retailer's privatelabel credit card), the electronic device determines whether a paymentaccount selection condition is met (e.g., determining whether the userhas previously approved automatically using a particular payment accountof the particular payment account type at this location). In accordancewith a determination that the payment account selection condition is notmet (e.g., user has not previously approved automatically using theparticular payment account at this location), the electronic deviceforgoes proceeding with the payment transaction using a payment accountof the particular payment account type (e.g., forgoing transmitting anidentifier, such as a PAN, of the requested particular payment accountto the contactless payment terminal). Thus, if the device has notpreviously received user approved to automatically provide the requestedpayment account to the requesting merchant, the electronic device doesnot provide payment account information of the requested payment accountto the contactless payment terminal 610.

In accordance with some embodiments, in accordance with thedetermination that the request comprises the request for payment usingthe particular payment account type and in accordance with adetermination that the payment account selection condition is met (e.g.,the user has previously approved automatically using the particularpayment account at this location), the electronic device proceeds withthe payment transaction using the payment account (e.g., based onpayment account information stored in an electronic wallet of thedevice) of the particular payment account type (e.g., transmitting anidentifier, such as a PAN, of the requested particular payment accountto the contactless payment terminal). Thus, if the device has previouslyreceived user approved to automatically provide the requested paymentaccount to the requesting merchant, the electronic device providespayment account information of the requested payment account to thecontactless payment terminal 610. As illustrated in FIG. 12C, theelectronic device may display an indication 1204 of the requestedpayment account to notify the user that the default payment account willbe used in the payment transaction. For example, the payment accounttype that is requested may identify SHOPCO private label cards.

In accordance with some embodiments, in accordance with thedetermination that the request comprises the request for payment usingthe particular payment account type and in accordance with thedetermination that the payment account selection condition is not met(e.g., user has not previously approved automatically using theparticular payment account at this location), the electronic devicerequests authorization (e.g., from a user) to proceed with the paymenttransaction using the payment account of the particular payment accounttype. In some embodiments, requesting authorization from the userincludes displaying an affordance or visual object (1208 of FIG. 12D)for confirmation that the payment account should be used. Authorizationto proceed may comprise detecting a respective fingerprint on afingerprint sensor of the electronic device, wherein the fingerprint isdetermined to be consistent with an enrolled fingerprint that is enabledto authorize payment transactions, or removing the device from the NFCfield and replacing the device in the NFC field while the finger ismaintained on the fingerprint sensor. For authorization using afingerprint, the device stores information about one or morefingerprints of the user to use for determining whether a respectivefingerprint is enabled to authorize payment transactions. For example,when the device detects the user: (1) pulling the device out of the NFCfield to look at the payment account that has been requested and then(2) placing the device back into the NFC field without switching cards(e.g., by swiping between cards or by tilting the device), it is anindication that the user is authorizing the use of the requested paymentaccount. Authorization to proceed may also comprise receiving a passcodevia a touch-sensitive surface of the electronic device, the passcodebeing determined to be consistent with an enrolled passcode that isenabled to authorize payment transactions.

In accordance with some embodiments, in accordance with thedetermination that the request comprises the request for payment usingthe particular payment account type and in accordance with thedetermination that the payment account selection condition is not met(e.g., user has not previously approved automatically using theparticular payment account at this location): the electronic devicereceives a user input (e.g., detects left tilt or right tilt, receives aleft or right swipe on a display, detects shaking of the device,receives click of a home button, detects a swipe on the home button,etc.); and in response to receiving the user input, the electronicdevice provides an indication (e.g., 1210 of FIG. 12E) that a secondpayment account different from the payment account of the particularpayment account type will be used for proceeding with the paymenttransaction. In some embodiments, in response to detecting the userplacing the device back into the field of the contactless paymentterminal (e.g., after the electronic device receives the user input tochange the payment account), the device transmits an identifier, such asa PAN, of the second payment account to the contactless paymentterminal. Thus, when a device requests payment using a particularpayment account that the user has not previously authorized for use inpayment transactions at the location, the device provides the user withan opportunity to change the payment account to a desired paymentaccount.

In accordance with some embodiments, as illustrated in FIG. 12E, thesecond payment account is the default payment account.

In accordance with some embodiments, the payment account selectioncondition is not met when: the contactless payment terminal 610 is of afirst type (e.g., a contactless payment terminal of a particularretailer, at a particular location, or is a particular POS terminal),and the device has not previously received approval from a user to usethe particular payment account of the particular payment account type atcontactless payment terminals of the first type in the absence of inputspecifying a different payment account before the device receivesauthorization to proceed with a payment transaction using the device.For example, when the device has not previously received approval fromthe user to use a particular payment account at a particular retailer,the payment account selection condition is not met when a contactlesspayment terminal of the retailer requests that particular paymentaccount.

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device receives averified request (e.g., with digital signature authorized to accesscard) from the contactless payment terminal 610 (e.g., the paymentaccount selection condition is not met and the device forgoes proceedingwith the payment transaction using a payment account of the particularpayment account type if the request from the contactless paymentterminal 610 is not verified).

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device haspreviously proceeded with one or more payment transactions at thecontactless payment terminal 610 using the payment account of theparticular payment account type. For example, the payment accountselection condition is not met and the device forgoes proceeding withthe payment transaction using a payment account of the particularpayment account type if the device has not previously proceeded with oneor more payment transactions at the contactless payment terminal usingthe payment account of the particular payment account type. Thus, if auser has previously approved using the requested payment account at thecontactless payment terminal 610, the condition is met and a subsequentauthorization is not required when the contactless payment terminal 610requests the same payment account during a subsequent paymenttransaction.

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device haspreviously proceeded with one or more payment transactions at a location(e.g., within a predefined geographical area, such as a store, a city, astate, or a country) that is associated with the contactless paymentterminal using the payment account of the particular payment accounttype. For example, the payment account selection condition is not metand the device forgoes proceeding with the payment transaction using apayment account of the particular payment account type if the device hasnot previously proceeded with one or more payment transactions at alocation that is associated with the contactless payment terminal usingthe payment account of the particular payment account type.

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device haspreviously proceeded with one or more payment transactions at thecontactless payment terminal using the payment account of the particularpayment account type. For example, the payment account selectioncondition is not met and the device forgoes proceeding with the paymenttransaction using a payment account of the particular payment accounttype if the device has not previously proceeded with one or more paymenttransactions at the contactless payment terminal using the paymentaccount of the particular payment account type.

In accordance with some embodiments, prior to receiving the request(e.g., for payment account information or loyalty account information ofa loyalty account) associated with the payment transaction: theelectronic device receives (e.g., from a user) payment accountinformation for the particular payment account (e.g., for linking thepayment account to the device using an electronic wallet) and theelectronic device receives user input indicating whether the particularpayment account should be used at contactless payment terminals of afirst type (e.g., a contactless payment terminal of a particularretailer, at a particular location, or is a particular POS terminal) inthe absence of input specifying a different payment account before thedevice receives authorization to proceed with a payment transactionusing the device. If the device has previously received input indicatingthe particular payment account should be used at contactless paymentterminals of the first type, the payment account selection conditionwill be met when contactless payment terminals of the first type requestpayment using the particular payment account.

In accordance with some embodiments, an electronic wallet of theelectronic device includes one or more different payment accountsassociated with a user of the electronic device, the one or moredifferent payment accounts being different from the particular paymentaccount (e.g., the particular payment account used for the paymenttransaction). In some embodiments, when the device detects the devicebeing placed into the field of the contactless payment terminal, thedevice transmits an identifier, such as a PAN, of a selected paymentaccount (from among the one or more different payment accounts) to thecontactless payment terminal that enables the contactless paymentterminal to engage in the payment transaction.

In accordance with some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction. For example, payment account information is transmittedfrom the electronic device to a contactless payment terminal using NFCfor engaging in the payment transaction.

FIG. 13 is a flow diagram illustrating a method for proceeding with apayment transaction using a payment account of a requested paymentaccount type, in accordance with some embodiments. Method 1300 isperformed at a device (e.g., 100, 300, 500) with one or more wirelesscommunication elements (e.g., one or more wireless antennas such as NFCantennas, WiFi antennas, etc.). Some operations in method 1300 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 1300 provides an intuitive way for proceedingwith a payment transaction using a payment account of a requestedpayment account type, in accordance with some embodiments. The methodreduces the cognitive burden on a user for proceeding with a paymenttransaction using a payment account of a requested payment account type,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, proceeding with a paymenttransaction using a payment account of a requested payment account typefaster and more efficiently conserves power and increases the timebetween battery charges.

At block 1302, the electronic device receives, from a contactlesspayment terminal (e.g., 610; a contactless payment terminal that usesNFC to communication with the electronic device) via the one or morewireless communication elements, a request (e.g., for payment accountinformation of a payment account or loyalty account information of aloyalty account) associated with a payment transaction.

At block 1304, the electronic device determines whether the requestcomprises a request for payment using a particular payment account type(e.g., a particular retailer's private label credit card).

At block 1306, in accordance with a determination that the request doesnot comprise the request for payment using the particular paymentaccount type, the electronic device proceeds with the paymenttransaction using a default payment account (e.g., transmitting anidentifier, such as a PAN, of the requested particular payment accountto the contactless payment terminal).

At block 1308, in accordance with a determination that the requestcomprises the request for payment using the particular payment accounttype (e.g., contactless payment terminal requests a particularretailer's private label credit card), the device proceeds to block1310.

At block 1310, the electronic device determines whether a paymentaccount selection condition is met (e.g., determining whether the userhas previously approved automatically using a particular payment accountof the particular payment account type at this location).

At block 1312, in accordance with a determination that the paymentaccount selection condition is not met (e.g., user has not previouslyapproved automatically using the particular payment account at thislocation), the electronic device forgoes proceeding with the paymenttransaction using a payment account of the particular payment accounttype (e.g., forgoing transmitting an identifier, such as a PAN, of therequested particular payment account to the contactless paymentterminal).

In accordance with some embodiments, at block 1314, in accordance withthe determination that the request comprises the request for paymentusing the particular payment account type and in accordance with adetermination that the payment account selection condition is met (e.g.,user has previously approved automatically using the particular paymentaccount at this location), the electronic device proceeds with thepayment transaction using the payment account (e.g., based on paymentaccount information stored in an electronic wallet of the device) of theparticular payment account type (e.g., transmitting an identifier, suchas a PAN, of the requested particular payment account to the contactlesspayment terminal).

In accordance with some embodiments, in accordance with thedetermination that the request comprises the request for payment usingthe particular payment account type and in accordance with thedetermination that the payment account selection condition is not met(e.g., user has not previously approved automatically using theparticular payment account at this location), the electronic devicerequests authorization (e.g., from a user) to proceed with the paymenttransaction using the payment account of the particular payment accounttype. In some embodiments, requesting authorization from the userincludes displaying an affordance or visual object (e.g., 1208) forconfirmation that the payment account should be used. Authorization toproceed may comprise detecting a respective fingerprint on a fingerprintsensor of the electronic device, wherein the fingerprint is determinedto be consistent with an enrolled fingerprint that is enabled toauthorize payment transactions, or removing the device from the NFCfield and replacing the device in the NFC field while the finger ismaintained on the fingerprint sensor. For authorization using afingerprint, the device stores information about one or morefingerprints of the user to use for determining whether a respectivefingerprint is enabled to authorize payment transactions. For example,the device detects: (1) the user pulling the device out of the NFC fieldto look at the payment account that has been requested and then (2)placing the device back into the NFC field without receiving input toswitch cards (e.g., by receiving a swipe between cards or by detectingtilting of the device), it is an indication that the user is authorizingthe use of the requested payment account. In some examples,authorization to proceed comprises receiving a passcode via atouch-sensitive surface of the electronic device, the passcode beingdetermined to be consistent with an enrolled passcode that is enabled toauthorize payment transactions.

In accordance with some embodiments, in accordance with thedetermination that the request comprises the request for payment usingthe particular payment account type and in accordance with thedetermination that the payment account selection condition is not met(e.g., user has not previously approved automatically using theparticular payment account at this location): the electronic devicereceives a user input (e.g., detects left tilt or right tilt, receives aleft or right swipe on a display, detects shaking of the device,receives click of a home button, detects a swipe on the home button,etc.); and in response to receiving the user input, the electronicdevice provides an indication (e.g., 1210 of FIG. 12E) that a secondpayment account different from the payment account of the particularpayment account type will be used for proceeding with the paymenttransaction. In some embodiments, when the device detects that the userplaces the device back into the field of the contactless paymentterminal (e.g., after the electronic device receives the user input tochange the payment account), the device transmits an identifier, such asa PAN, of the second payment account to the contactless paymentterminal. Thus, when a device requests payment using a particularpayment account that the user has not previously authorized for use inpayment transactions at the location, the device provides the user withan opportunity to change the payment account to a desired paymentaccount.

In accordance with some embodiments, the second payment account is thedefault payment account.

In accordance with some embodiments, the payment account selectioncondition is not met when: the contactless payment terminal (e.g., 610)is of a first type (e.g., a contactless payment terminal of a particularretailer, at a particular location, or is a particular POS terminal),and the device has not previously received approval from a user to usethe particular payment account of the particular payment account type atcontactless payment terminals of the first type in the absence of inputspecifying a different payment account before the device receivesauthorization to proceed with a payment transaction using the device.For example, when the device has not previously received approval to usea particular payment account at a particular retailer, the paymentaccount selection condition is not met when a contactless paymentterminal of the retailer requests that particular payment account.

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device receives averified request (e.g., with digital signature authorized to accesscard) from the contactless payment terminal (e.g., 610; the paymentaccount selection condition is not met and the device forgoes proceedingwith the payment transaction using a payment account of the particularpayment account type if the request from the contactless paymentterminal 610 is not verified).

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device haspreviously proceeded with one or more payment transactions at thecontactless payment terminal (e.g., 610) using the payment account ofthe particular payment account type. For example, the payment accountselection condition is not met and the device forgoes proceeding withthe payment transaction using a payment account of the particularpayment account type if the device has not previously proceeded with oneor more payment transactions at the contactless payment terminal usingthe payment account of the particular payment account type. Thus, if auser has previously approved using the requested payment account at thecontactless payment terminal (e.g., 610), the condition is met and asubsequent authorization is not required when the contactless paymentterminal (e.g., 610) requests the same payment account during asubsequent payment transaction.

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device haspreviously proceeded with one or more payment transactions at a location(e.g., within a predefined geographical area, such as a store, a city, astate, or a country) that is associated with the contactless paymentterminal using the payment account of the particular payment accounttype. For example, the payment account selection condition is not metand the device forgoes proceeding with the payment transaction using apayment account of the particular payment account type if the device hasnot previously proceeded with one or more payment transactions at alocation that is associated with the contactless payment terminal usingthe payment account of the particular payment account type.

In accordance with some embodiments, the payment account selectioncondition includes a criterion that is met when the device haspreviously proceeded with one or more payment transactions at thecontactless payment terminal using the payment account of the particularpayment account type. For example, the payment account selectioncondition is not met and the device forgoes proceeding with the paymenttransaction using a payment account of the particular payment accounttype if the device has not previously proceeded with one or more paymenttransactions at the contactless payment terminal using the paymentaccount of the particular payment account type.

In accordance with some embodiments, prior to receiving the request(e.g., for payment account information or loyalty account information ofa loyalty account) associated with the payment transaction: theelectronic device receives (e.g., from a user) payment accountinformation for the particular payment account (e.g., for linking thepayment account to the device using an electronic wallet) and theelectronic device receives user input indicating whether the particularpayment account should be used at contactless payment terminals of afirst type (e.g., a contactless payment terminal of a particularretailer, at a particular location, or is a particular POS terminal) inthe absence of input specifying a different payment account before thedevice receives authorization to proceed with a payment transactionusing the device. If the device does receive user input indicating theparticular payment account should be used at contactless paymentterminals of the first type, the payment account selection conditionwill be met when contactless payment terminals of the first type requestpayment using the particular payment account.

In accordance with some embodiments, an electronic wallet of theelectronic device includes one or more different payment accountsassociated with a user of the electronic device, the one or moredifferent payment accounts being different from the particular paymentaccount (e.g., the particular payment account used for the paymenttransaction). In some embodiments, the device detects that the user hasplaced the device into the field of the contactless payment terminal,and in response, the device transmits an identifier, such as a PAN, of aselected payment account (from among the one or more different paymentaccounts) to the contactless payment terminal that enables thecontactless payment terminal to engage in the payment transaction.

In accordance with some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction. For example, payment account information may be transmittedfrom the electronic device to a contactless payment terminal using NFCfor engaging in the payment transaction.

Note that details of the processes described above with respect tomethod 1300 (e.g., FIG. 13) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1100, 1500, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1300. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1100,1500, 1700, and 1900 optionally have one or more of the characteristicsof the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1300. For brevity, these details are not repeated below.

FIGS. 14A-14E illustrate exemplary techniques and exemplary userinterfaces for providing indications of payments accounts for use atparticular locations, in accordance with some embodiments. For example,an electronic device 100 with a location sensor (e.g., GPS receiver,bluetooth receiver, WLAN receiver) and a display is used by thetechnique. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIG. 15.

Some accounts, such as private label accounts or loyalty accounts, maybe associated with particular locations (e.g., a particular merchant ora particular store of a merchant), but the payment terminals of thoselocations do not request (or are not capable of requesting) theassociated account. These locations may be associated with prompting foruse of the associated account (e.g., for when the electronic device isat the location). To accommodate such terminals, the electronic devicemay prompt the user when the device determines that the device is atsuch a location and determines that the user prefers to use an accountthat is associated with the current location. Thus, when a user is in astore and the user's device is provisioned with a private label paymentaccount that is associated with the store, the user is notified that theprivate label payment account is available for use if that store'sterminals do not support requesting specific cards.

For example, a user may enter a particular store associated with aprivate label account for which the user has specified the private labelaccount should be used at the store. If the store's terminals are notcapable of requesting the private label account, the device provides analert that the private label account can be used at that store. Foranother example, a user may enter a particular store associated with aprivate label account for which the user has specified the private labelaccount should not be used at the store. The device forgoes providing analert that the private label account can be used at that store, even ifthe store's terminals are not capable of requesting the private labelaccount. For another example, a user may enter a particular storeassociated with a private label account for which the user has specifiedthe private label account should be used at the store. If the store'sterminals are capable of requesting the private label account, thedevice forgoes providing an alert that the private label account can beused at that store. In this last example, the notification is not neededbecause the store's payment terminal can request the private labelaccount.

The electronic device detects, using the location sensor, that a currentlocation (e.g., determining that the device is physically located at aparticular retailer or a particular store of a particular retailer) isassociated with prompting for use of a particular payment account (e.g.,determining that a particular private label payment account isassociated with the retailer and that the terminals at the retailer arenot capable of requesting particular payment accounts).

In response to detecting that the current location is associated withprompting for use of the particular payment account, the electronicdevice determines whether the electronic device has previously receivedan indication of a user preference (e.g., a stored setting indicatingthe user preference) to use the particular payment account at thecurrent location (e.g., the user previously expressly approved the useof the particular payment account at this particular retailer, even ifnot at this particular store of the retailer). Similar to thedescription of affordance 622 of FIG. 6E, a user can provide anindication of the user preference when first linking the account to theelectronic device or at a later time.

As illustrated in FIG. 14A, in accordance with a determination that thedevice has previously received an indication of the user preferenceassociated with using the particular payment account at the currentlocation (e.g., the user has approved use of the particular paymentaccount at the current store), the electronic device displays, on thedisplay, a visual indication 1402 that the particular payment account isavailable for use at the location (e.g., prompts the user).

In accordance with a determination that the device has not previouslyreceived an indication of the user preference associated with using theparticular payment account at the current location (e.g., the user hasnot specified any preference (either approved or rejected) or the userhas specified a preference to not use the particular payment account atthe current store), the electronic device forgoes displaying, on thedisplay, the visual indication that the particular payment account isavailable for use at the location (e.g., forgoes prompting the user).

As illustrated in FIG. 14B, in accordance with some embodiments,displaying, on the display, the visual indication comprises displaying avisual indication 1404 that the particular payment account will be usedfor a payment transaction conducted at the current location in theabsence of input specifying a different payment account before thedevice receives authorization to proceed with a payment transactionusing the device. In some examples, the user can provide input (e.g., byswiping a touch-sensitive surface at a location associated with thevisual indication 1404) to decline automatically using the particularpayment account for a payment transaction conducted at the currentlocation. In this example, if the visual indication 1404 that theparticular payment account will be used is displayed and the userprovides payment input (e.g., by placing the device into the NFC fieldwith their finger on the fingerprint sensor for authorization), thedevice will provide payment account information associated with theparticular payment account to the payment terminal, rather than paymentaccount information of the default payment account.

As illustrated in FIG. 14C, in accordance with some embodiments,displaying, on the display, the visual indication comprises displaying avisual indication 1406 recommending that the particular payment accountbe used for a payment transaction conducted at the current location. AtFIG. 14D, the electronic device receives user input accepting therecommendation (e.g., the user activates an affordance of visualindication 1406 by swiping a touch-sensitive surface at a locationassociated with the visual indication 1406). The electronic deviceprepares (e.g., in response to the user input accepting therecommendation) the particular payment account for use at a contactlesspayment terminal at the current location. As illustrated in FIG. 14E,the device displays an electronic wallet indicating that the paymentaccount is ready for use at a contactless payment terminal. In thisexample, the device receives user input (e.g., swipe on atouch-sensitive surface at a location associated with the visualindication 1406) to approve or request that the device automaticallyusing the particular payment account for the payment transactionconducted at the current location. In some examples, the device displaysaffordances (e.g., 1412, 1414, 1416), which when activated, change theselection of the payment account.

In accordance with some embodiments, the current location is based onone or more of received short-range communication (e.g., Bluetooth orNFC) signals and received GPS signals. For example, the device maydetermine (based on a Bluetooth signal) that the device is inside astore of a particular retail chain, although the device may not knowwhich store of the particular retail chain.

In accordance with some embodiments, the electronic device includes ashort-range communication radio. Subsequent to determining whether theelectronic device has previously received an indication of a userpreference: the electronic device detects, by the short-rangecommunication radio, presence of a field generated by a contactlesspayment terminal while authorization to proceed with the paymenttransaction has not been provided; in response to detecting presence ofthe field generated by the contactless payment terminal authorization toproceed with the payment transaction has not been provided, theelectronic device provides a prompt (e.g., an audible, visible, orhaptic output provided to the user) to authorize payment; afterproviding the prompt, the electronic device receives user inputselecting a second payment account for use in a payment transaction atthe current location; and in response to receiving the user inputselecting the second payment account, the electronic device prepares touse the second payment account in the payment transaction at the currentlocation (e.g., arming the device to provide payment account informationfor the second payment account and/or prompting the user to provideauthorization to use the second payment account for the paymenttransaction).

In accordance with some embodiments, an electronic wallet of theelectronic device includes one or more different payment accountsassociated with a user of the electronic device, the one or moredifferent payment accounts being different from the particular paymentaccount (e.g., the particular payment account available for use at thecurrent location). In some embodiments, when the device detects that theuser has placed the device into the field of the contactless paymentterminal, the device transmits an identifier, such as a PAN, of aselected payment account (from among the one or more different paymentaccounts and the particular payment account) to the contactless paymentterminal. The identified enables the contactless payment terminal toengage in a payment transaction.

In some embodiments, engaging in the payment transaction includesrouting information to one or more financial institutions to verifypayment credentials and/or receive authorization to complete thetransaction. For example, payment account information may be transmittedfrom the electronic device to a contactless payment terminal using NFCfor engaging in the payment transaction.

In some embodiments, as illustrated in FIG. 14E, the device requestsauthorization from the user prior to proceeding with a paymenttransaction. Requesting authorization from the user may comprisedisplaying an affordance (e.g., 1418) for confirmation that the paymentaccount should be used. Authorization to proceed may comprise detectinga respective fingerprint on the fingerprint sensor of the electronicdevice that is determined to be consistent with an enrolled fingerprintthat is enabled to authorize payment transactions. Authorization toproceed may comprise receiving a passcode via a touch-sensitive surfaceof the electronic device, the passcode being determined to be consistentwith an enrolled passcode that is enabled to authorize paymenttransactions. For authorization using a fingerprint, the device storesinformation about one or more fingerprints of the user to use fordetermining whether a respective fingerprint is enabled to authorizepayment transactions.

FIG. 15 is a flow diagram illustrating a method for providingindications of payments accounts for use at particular locations, inaccordance with some embodiments. Method 1500 is performed at a device(e.g., 100, 300, 500) with a location sensor (e.g., GPS receiver,bluetooth receiver, WLAN receiver) and a display. Some operations inmethod 1500 may be combined, the order of some operations may bechanged, and some operations may be omitted.

As described below, method 1500 provides an intuitive way for providingindications of payments accounts for use at particular locations, inaccordance with some embodiments. The method reduces the cognitiveburden on a user for selecting payments accounts for use at particularlocations, thereby creating a more efficient human-machine interface.For battery-operated computing devices, providing indications ofpayments accounts for use at particular locations faster and moreefficiently conserves power and increases the time between batterycharges.

At block 1502, the electronic device detects, using the location sensor,that a current location (e.g., determining that the device is physicallylocated at a particular retailer or a particular store of a particularretailer) is associated with prompting for use of a particular paymentaccount (e.g., determining that a particular private label paymentaccount is associated with the retailer and that the terminals at theretailer are not capable of requesting particular payment accounts).

At block 1504, in response to detecting that the current location isassociated with prompting for use of the particular payment account, thetechnique proceeds to block 1506.

At block 1506, the electronic device determines whether the electronicdevice has previously received an indication of a user preference (e.g.,a stored setting indicating the user preference) associated with usingthe particular payment account at the current location (e.g., the userpreviously expressly approved the use of the particular payment accountat this particular retailer, even if not at this particular store of theretailer).

At block 1508, in accordance with a determination that the device haspreviously received an indication of the user preference associated withusing the particular payment account at the current location (e.g., theuser has approved use of the particular payment account at the currentstore), the electronic device displays, on the display, a visualindication (e.g., 1402, 1404, or 1406) that the particular paymentaccount is available for use at the location.

At block 1510, in accordance with a determination that the device hasnot previously received an indication of the user preference associatedwith using the particular payment account at the current location (e.g.,the user has not specified any preference (either approved or rejected)or the user has specified a preference to not use the particular paymentaccount at the current store), forgoing displaying, on the display, thevisual indication that the particular payment account is available foruse at the location.

In accordance with some embodiments, displaying, on the display, thevisual indication comprises displaying a visual indication (e.g., 1404)that the particular payment account will be used for a paymenttransaction conducted at the current location in the absence of inputspecifying a different payment account before the device receivesauthorization to proceed with a payment transaction using the device. Insome examples, the user can provide input (e.g., by swiping atouch-sensitive surface at a location associated with the visualindication 1404) to decline automatically using the particular paymentaccount for a payment transaction conducted at the current location. Inthis example, if the visual indication 1404 that the particular paymentaccount will be used is displayed and the user provides payment input(e.g., by placing the device into the NFC field with their finger on thefingerprint sensor for authorization), the device will provide paymentaccount information associated with the particular payment account tothe payment terminal, rather than payment account information of thedefault payment account.

In accordance with some embodiments, displaying, on the display, thevisual indication comprises displaying a visual indication (e.g., 1406)recommending that the particular payment account be used for a paymenttransaction conducted at the current location. The electronic devicereceives user input accepting the recommendation (e.g., the useractivates an affordance of visual indication (e.g., 1406) by swiping atouch-sensitive surface at a location associated with the visualindication 1406), and the electronic device prepares (e.g., in responseto the user input accepting the recommendation) the particular paymentaccount for use at a contactless payment terminal at the currentlocation. In this example, the user can provide input (e.g., by swipinga touch-sensitive surface at a location associated with the visualindication 1406) to approve or request that the device automaticallyusing the particular payment account for the payment transactionconducted at the current location.

In accordance with some embodiments, the current location is based onone or more of received short-range communication (e.g., Bluetooth orNFC) signals and received GPS signals. For example, the device maydetermine (based on a Bluetooth signal) that the device is inside astore of a particular retail chain, although the device may not knowwhich store of the particular retail chain.

In accordance with some embodiments, the electronic device includes ashort-range communication radio. Subsequent to determining whether theelectronic device has previously received an indication of a userpreference: the electronic device detects, by the short-rangecommunication radio, presence of a field generated by a contactlesspayment terminal while authorization to proceed with the paymenttransaction has not been provided; in response to detecting presence ofthe field generated by the contactless payment terminal authorization toproceed with the payment transaction has not been provided, theelectronic device provides a prompt (e.g., an audible, visible, orhaptic output provided to the user) to authorize payment; afterproviding the prompt, the electronic device receives user inputselecting a second payment account for use in a payment transaction atthe current location; and in response to receiving the user inputselecting the second payment account, the electronic device prepares touse the second payment account in the payment transaction at the currentlocation (e.g., arming the device to provide payment account informationfor the second payment account and/or prompting the user to provideauthorization to use the second payment account for the paymenttransaction).

In accordance with some embodiments, an electronic wallet of theelectronic device includes one or more different payment accountsassociated with a user of the electronic device, the one or moredifferent payment accounts being different from the particular paymentaccount (e.g., the particular payment account available for use at thecurrent location). In some embodiments, when the device detects that theuser has placed the device into the field of the contactless paymentterminal, the device transmits an identifier, such as a PAN, of aselected payment account (from among the one or more different paymentaccounts and the particular payment account) to the contactless paymentterminal. The identified enables the contactless payment terminal toengage in a payment transaction.

In some embodiments, engaging in the payment transaction includesrouting information to one or more financial institutions to verifypayment credentials and/or receive authorization to complete thetransaction. For example, payment account information may be transmittedfrom the electronic device to a contactless payment terminal using NFCfor engaging in the payment transaction. An exemplary payment networkarchitecture and additional details regarding routing for paymenttransactions can be found at, for example, FIG. 5C and the accompanyingdescriptions of the current application and FIG. 2 and the accompanyingdescription of U.S. Patent Application Ser. No. 62/004,338, entitled“USER DEVICE SECURE PARTICIPATION IN TRANSACTIONS VIA LOCAL SECUREELEMENT DETECTION OF MECHANICAL INPUT”, filed May 29, 2014, (ReferenceNo. P22931USP1).

In some embodiments, the device requests authorization from the userprior to proceeding with a payment transaction. Requesting authorizationfrom the user may comprise displaying an affordance for confirmationthat the payment account should be used. Authorization to proceed maycomprise detecting a respective fingerprint on the fingerprint sensor ofthe electronic device that is determined to be consistent with anenrolled fingerprint that is enabled to authorize payment transactions.Authorization to proceed may comprise receiving a passcode via atouch-sensitive surface of the electronic device, the passcode beingdetermined to be consistent with an enrolled passcode that is enabled toauthorize payment transactions. For authorization using a fingerprint,the device stores information about one or more fingerprints of the userto use for determining whether a respective fingerprint is enabled toauthorize payment transactions.

Note that details of the processes described above with respect tomethod 1500 (e.g., FIG. 15) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1100, 1300, 1700, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1500. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1100,1300, 1700, and 1900 optionally have one or more of the characteristicsof the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1500. For brevity, these details are not repeated below.

FIGS. 16A-16G illustrate exemplary techniques and exemplary userinterfaces for displaying multiple payment accounts grouped together, inaccordance with some embodiments. For example, an electronic device 100with a display and one or more input devices (e.g., touch-sensitivesurface, camera sensor) is used by the technique. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 17.

Some financial institutions provide customers with a single physicalpayment card (e.g., a credit/debit card) that supports multiplefinancial networks (e.g., processing using both a debit card rail and acredit card rail). For example, if a traditional payment card is used ata swipe payment terminal and the card owner chooses to process thetransaction as a credit card, the transaction will generally go over acredit rail (e.g., a credit card processor's gateway) and not a debitrail (e.g., a bank's debit card gateway). Such payment cards are said tobe associated with multiple payment accounts (e.g., a credit paymentaccount and a debit payment account). An exemplary payment networkarchitecture and additional details regarding routing for paymenttransactions can be found at, for example, FIG. 2 and the accompanyingdescription of U.S. Patent Application Ser. No. 62/004,338, entitled“USER DEVICE SECURE PARTICIPATION IN TRANSACTIONS VIA LOCAL SECUREELEMENT DETECTION OF MECHANICAL INPUT”, filed May 29, 2014, (ReferenceNo. P22931USP1).

When provisioning an electronic device for such payment cards (e.g.,linking the multiple payment accounts of the payment card to anelectronic wallet of the electronic device), it is advantageous to groupthe multiple payment accounts together for easy viewing and selection bya user. The description below provides additional details for thistechnique.

FIG. 16A illustrates a technique by which a user requests to linkpayment card 1602 with the electronic device 100. In this example, theuser is using a camera sensor (e.g., an input device) of the electronicdevice 100 (e.g., on the back of the electronic device 100) to capturean image that includes a portion of the payment card 1602, which isdisplayed in viewfinder 1604. This user interface also provides anaffordance 1606, which when activated allows the user to manually enteraccount information for the payment card 1602.

The electronic device receives, via the one or more input devices, arequest (e.g., manual entry on a touch-sensitive display, importing froma server, or input using a camera sensor of the electronic device) tolink a payment card with the electronic device, the request comprisingaccount information (e.g., card number, card expiration date, name oncard).

In response to receiving the request via the one or more input devices,the electronic device determines whether the payment card 1602 isassociated with multiple payment accounts (e.g., the payment card 1602may be associated with a credit account, a debit account, and a savingsaccount).

As illustrated in FIG. 16B, in accordance with a determination that thepayment card 1602 is associated with multiple payment accounts, (e.g.,after linking the multiple payment accounts to the electronic device)the electronic device displays, on the display, a payment accountinterface for the payment card that enables user selection amongmultiple payment accounts of the payment card (e.g., the credit accountand the debit account). For example, the payment account interface ofFIG. 16B includes a visual representation 1608 of the payment card 1602.The visual representation 1608 may have the same background art as thepayment card 1602 to indicate to the user that the visual representation1608 represents the payment card 1602. The payment account interface ofFIG. 16B includes a plurality of affordances (e.g., 1610, 1612, and1614) for the multiple payment accounts associated with the payment card1602. The payment account interface of FIG. 16B includes a visualrepresentation 1620 of a second payment card and a visual representation1630 of a third payment card. The visual representations 1608, 1620, and1630 of the payment cards may be arranged in a column (e.g.,vertically), while the plurality of affordances (e.g., 1610, 1612, and1614) for the multiple payment accounts of the payment card 1602 may bearranged in a row (e.g., horizontally). In some examples, an affordanceof a selected payment account (e.g., 1612) may have visualcharacteristics to indicate that it is selected, such as having adifferent color, a background, or text with a different font as comparedto an affordance of a payment account that is not selected (e.g., 1610).

In accordance with some embodiments, activating an affordance of apayment account changes the visual characteristics of the affordance ofthe newly selected payment account. For example, in FIG. 16C, affordance1614 has been selected. As a result, the visual characteristics ofaffordance 1614 have changed (as compared to FIG. 16B) to indicate thatthe payment account associated with affordance 1614 is selected.

In accordance with a determination that the payment card 1602 is notassociated with multiple payment accounts, the electronic devicedisplays, on the display, a payment account interface for the paymentcard that does not enable user selection among multiple payment accountsof the payment card (e.g., only a single displayed visual representationfor the payment card).

As illustrated in FIG. 16A, in accordance with some embodiments, theelectronic device includes a camera sensor and the request to link thepayment card with the electronic device is based on an image 1604 of thepayment card 1602, wherein the image is captured by the camera sensor ofthe electronic device.

In accordance with some embodiments, the payment card 1602 is associatedwith multiple payment accounts and the payment account interface for thepayment card 1602 includes a plurality of affordances (e.g., 1610, 1612,and 1614) for the multiple payment accounts associated with the paymentcard 1602. For example, each affordance (e.g., 1610, 1612, and 1614)corresponds to one of the multiple payment accounts. In some examples,activation of an affordance (e.g., 1610, 1612, and 1614) causes thedevice to display, on the display, information that is specific to thepayment account associated with the activated affordance.

In accordance with some embodiments, the plurality of affordances (e.g.,1610, 1612, and 1614) are grouped together to indicate that they relateto a single payment card (e.g., the payment card). In accordance withsome embodiments, the plurality of affordances (e.g., 1610, 1612, and1614) are displayed in a row.

In accordance with some embodiments, the electronic device includes atouch-sensitive surface. As illustrated in FIG. 16D, the electronicdevice receives, at the touch-sensitive surface, a vertical swipe input.As illustrated in FIG. 16E, in response to receiving the vertical swipeinput, displaying a plurality of affordances (e.g., 1608, 1620), whereina first card affordance 1608 of the plurality of affordances (e.g.,1608, 1620) represents a first group of multiple payment accounts and asecond card affordance 1620 of the plurality of affordances represents asecond group of multiple payment accounts distinct from the first group.For example, the device detects a user can swipe and displays images ofpayment cards. The payment cards may each be associated with multiplepayment accounts specific to the payment cards.

In accordance with some embodiments, as illustrated in FIG. 16E, theelectronic device receives user input activating the first cardaffordance 1620. As illustrated in FIG. 16F, in response to receivingthe user input activating the first card affordance 1620, the electronicdevice displays a first set of account affordances (e.g., 1622, 1624)associated with the first group of multiple payment accounts.

In accordance with some embodiments, the user taps on a payment card tosee the multiple payment accounts associated with the payment card. Theuser can then right or left swipe (and/or right or left tilt the device)to cause the device to display a different card and the multiple paymentaccounts associated with the different card. In some embodiments,payment cards are stacked in a first direction (e.g., vertically) andpayment accounts for the same card can be navigated to by swiping in asecond direction (e.g., horizontally). In some embodiments, paymentcards that are different from the default payment card may be displayedbelow the default payment card.

In some embodiments, each payment account of the multiple paymentaccounts of the payment card is associated with a different paymentaccount information (e.g., with a different DPAN).

In accordance with some embodiments, some payment cards are notassociated with multiple payment accounts. As illustrated in FIG. 16G,visual representation 1630 of the third payment card, for example, isnot associated with multiple payment accounts.

In accordance with some embodiments, the displayed plurality ofaffordances (e.g., 1610, 1612, and 1614) for the multiple paymentaccounts of the payment card 1602 are based on a current location of theelectronic device. For example, the device may determine that the deviceis in a country that does not permit the user of a particular paymentaccount. Accordingly, the device may forgo displaying an affordance forthe non-permitted payment account of the payment card.

In accordance with some embodiments, the payment card is associated withmultiple payment accounts and the device includes a short-rangecommunication radio. The electronic device detects, by the short-rangecommunication radio, presence of a field generated by a contactlesspayment terminal. In response to detecting presence of the fieldgenerated by the contactless payment terminal, the electronic devicedetermines whether the contactless payment terminal supports a firsttype of payment account. In accordance with a determination thecontactless payment terminal does not support the first type of paymentaccount, the electronic device forgoes providing an option to select thepayment account of the payment card of the first type. For example, ifan NFC contactless payment terminal does not support payments usingchecking accounts, the device may not display the checking accountaffordance for the payment card. In another example, the device may grayout the checking account affordance for the payment card to indicatethat the checking account is not available for use. In accordance with adetermination the contactless payment terminal does support the firsttype of payment account, the device may display the affordance of thepayment account of the payment card of the first type.

In accordance with some embodiments, the payment card is associated withmultiple payment accounts and the payment account interface for thepayment card includes a plurality of affordances (e.g., 1610, 1612,1614) for the multiple payment accounts associated with the payment card1602. The plurality of affordances (e.g., 1610, 1612, 1614) aredisplayed based on a priority order. For example, the priority orderchanges based on a current location of the device, a preference of theuser, a received preference of a contactless payment terminal, or thecapabilities of a contactless payment terminal. For example, the devicemay receive a user preference indicating the user's preference to use achecking account of a payment card at a merchant. In response todetecting that the device is at a location associated with the merchant,the device orders the plurality of affordances to place the affordanceassociated with the checking account first in a row of affordances ofthe payment accounts of the payment card.

FIG. 17 is a flow diagram illustrating a method for displaying multiplepayment accounts grouped together, in accordance with some embodiments.Method 1700 is performed at a device (e.g., 100, 300, 500) a display andone or more input devices. Some operations in method 1700 may becombined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 1700 provides an intuitive way for displayingmultiple payment accounts grouped together, in accordance with someembodiments. The method reduces the cognitive burden on a user forselecting payments accounts, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,selecting payment accounts faster and more efficiently conserves powerand increases the time between battery charges.

At block 1702, the electronic device receives, via the one or more inputdevices, a request (e.g., manual entry, importing from a server, orinput using a camera sensor of the electronic device) to link a paymentcard (e.g., 1602) with the electronic device, the request comprisingaccount information (e.g., card number, card expiration date, name oncard).

At block 1704, in response to receiving the request via the one or moreinput devices, the process proceeds to block 1706.

At block 1706, the electronic device determines whether the payment card(e.g., 1602) is associated with multiple payment accounts (e.g., asingle physical payment card may be associated with a credit account anda separate debit account).

At block 1708, in accordance with a determination that the payment card(e.g., 1602) is associated with multiple payment accounts, theelectronic device displays, on the display, a payment account interface(e.g., as illustrated in FIG. 16B) for the payment card that enablesuser selection among multiple payment accounts of the payment card(e.g., the credit account and the debit account).

At block 1710, in accordance with a determination that the payment card(e.g., 1602) is not associated with multiple payment accounts,displaying, on the display, a payment account interface for the paymentcard (e.g., 1602) that does not enable user selection among multiplepayment accounts of the payment card (e.g., only a single displayedaccount for the payment card).

In accordance with some embodiments, the electronic device includes acamera sensor and the request to link the payment card (e.g., 1602) withthe electronic device is based on an image (e.g., 1604) of the paymentcard (e.g., 1602), wherein the image (e.g., 1604) is captured by thecamera sensor of the electronic device.

In accordance with some embodiments, the payment card (e.g., 1602) isassociated with multiple payment accounts and the payment accountinterface for the payment card (e.g., 1602) includes a plurality ofaffordances (e.g., 1610, 1612, and 1614) for the multiple paymentaccounts associated with the payment card (e.g., 1602). For example,each affordance (e.g., 1610, 1612, and 1614) corresponds to one of themultiple payment accounts. In some examples, activation of an affordance(e.g., 1610, 1612, and 1614) causes the device to display, on thedisplay, information that is specific to the payment account associatedwith the activated affordance.

In accordance with some embodiments, the plurality of affordances (e.g.,1610, 1612, and 1614) are grouped together to indicate that they relateto a single payment card (e.g., the payment card). In accordance withsome embodiments, the plurality of affordances (e.g., 1610, 1612, and1614) are displayed in a row.

In accordance with some embodiments, the electronic device includes atouch-sensitive surface. As illustrated in FIG. 16D, the electronicdevice receives, at the touch-sensitive surface, a vertical swipe input.As illustrated in FIG. 16E, in response to receiving the vertical swipeinput, displaying a plurality of affordances (e.g., 1608, 1620), whereina first card affordance 1608 of the plurality of affordances (e.g.,1608, 1620) represents a first group of multiple payment accounts and asecond card affordance 1620 of the plurality of affordances represents asecond group of multiple payment accounts distinct from the first group.For example, the device detects a user can swipe and displays images ofpayment cards. The payment cards may each be associated with multiplepayment accounts specific to the payment cards.

In accordance with some embodiments, the electronic device receives userinput activating the first card affordance (e.g., 1620). In response toreceiving the user input activating the first card affordance (e.g.,1620), the electronic device displays a first set of account affordances(e.g., 1622, 1624) associated with the first group of multiple paymentaccounts.

In accordance with some embodiments, the user taps on a payment card tosee the multiple payment accounts associated with the payment card. Theuser can then right or left swipe (and/or right or left tilt the device)to cause the device to display a different card and the multiple paymentaccounts associated with the different card. In some embodiments,payment cards are stacked in a first direction (e.g., vertically) andpayment accounts for the same card can be navigated to by swiping in asecond direction (e.g., horizontally). In some embodiments, paymentcards that are different from the default payment card may be displayedbelow the default payment card.

In some embodiments, each payment account of the multiple paymentaccounts of the payment card is associated with a different paymentaccount information (e.g., with a different DPAN).

In accordance with some embodiments, the displayed plurality ofaffordances (e.g., 1610, 1612, and 1614) for the multiple paymentaccounts of the payment card (e.g., 1602) are based on a currentlocation of the electronic device. For example, the device may determinethat the device is in a country that does not permit the user of aparticular payment account. Accordingly, the device may forgo displayingan affordance for the non-permitted payment account of the payment card.

In accordance with some embodiments, the payment card is associated withmultiple payment accounts and the device includes a short-rangecommunication radio. The electronic device detects, by the short-rangecommunication radio, presence of a field generated by a contactlesspayment terminal. In response to detecting presence of the fieldgenerated by the contactless payment terminal, the electronic devicedetermines whether the contactless payment terminal supports a firsttype of payment account. In accordance with a determination thecontactless payment terminal does not support the first type of paymentaccount, the electronic device forgoes providing an option to select thepayment account of the payment card of the first type. For example, ifan NFC contactless payment terminal does not support payments usingchecking accounts, the device may not display the checking accountaffordance for the payment card. In another example, the device may grayout the checking account affordance for the payment card to indicatethat the checking account is not available for use. In accordance with adetermination the contactless payment terminal does support the firsttype of payment account, the device may display the affordance of thepayment account of the payment card of the first type.

In accordance with some embodiments, the payment card is associated withmultiple payment accounts and the payment account interface for thepayment card includes a plurality of affordances (e.g., 1610, 1612,1614) for the multiple payment accounts associated with the payment card1602. The plurality of affordances (e.g., 1610, 1612, 1614) aredisplayed based on a priority order. For example, the priority order maychange based on a current location of the device, a received preferenceof a contactless payment terminal, or the capabilities of a contactlesspayment terminal.

Note that details of the processes described above with respect tomethod 1700 (e.g., FIG. 17) are also applicable in an analogous mannerto the methods described above and below. For example, methods 700, 900,1100, 1300, 1500, and 1900 may include one or more of thecharacteristics of the various methods described above with reference tomethod 1700. For example, the electronic wallet, payment accounts,loyalty accounts, affordances, and inputs of methods 700, 900, 1100,1300, 1500, and 1900 optionally have one or more of the characteristicsof the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of the electronic device described in method1700. For brevity, these details are not repeated below.

FIGS. 18A-18E illustrate exemplary techniques and exemplary userinterfaces for linking a payment account to an electronic device, inaccordance with some embodiments. For example, an electronic device 100with a display is used by the technique. The user interfaces in thesefigures are used to illustrate the processes described below, includingthe processes in FIG. 19.

In some circumstances, it is beneficial to allow an application (e.g., athird-party financial application) running on the electronic device toparticipate in the process for linking a payment card to the electronicdevice. For example, rather than requesting a user to input an accountnumber and expiration date of the payment card, an electronic walletapplication of the electronic device can receive the account numberand/or expiration date of the payment card from a financial applicationthat has access to the information. For example, the financialapplication may be an application that accesses financial records of thefinancial institution that issued the payment card.

At FIG. 18A, the electronic device displays a login user interface for afinancial application. The login user interface may display the identity1810 of the financial institution 1810, an entry field 1812 forreceiving a username, an entry field 1814 for receiving a user password1814, and a login affordance 1816 for initiating a process for accessingfinancial records associated with the user at a remote server of thefinancial institution. For example, the device may display the financialapplication (e.g., which prompts the user to log in) after the devicedetects a user request to add a payment account associated with thefinancial institution, but the device does not have access to therequired details of the payment account (e.g., the device detects thatthe payment account is serviced by the financial institution, but doesnot have access to the account number of the payment account).

As illustrated in FIG. 18B, the electronic device displays (e.g., afterthe user has logged in) a user interface for the financial application,wherein the financial application is one of a plurality of applicationson the electronic device. The financial application is a third-partyapplication that is associated with the financial institution. Thefinancial application is restricted from accessing a secured area of thedevice (e.g., a portion of memory) that is accessible by a first-partyelectronic wallet application. For example, the financial applicationhas less access to the secured area as compared to the electronic walletapplication. For another example, the financial application only haswrite access to the secured area.

While displaying the user interface for the financial application (e.g.,the user interface of FIG. 18B), the electronic device receives arequest (e.g., received from the financial application) to add a paymentaccount associated with the financial institution to the electronicwallet. For example, the request may be initiated when the devicereceives activation of affordance 1820 for linking a debit card to theelectronic device or when the device receives activation of affordance1822 for linking a credit card to the electronic wallet.

In response to receiving the request to add the payment accountassociated with the financial institution to the electronic wallet andin accordance with a determination that addition of the payment accountto the electronic wallet has been authorized, the electronic devicestores information associated with the payment account that is providedby the third-party application to the secured area of the device that isaccessible by the first-party electronic wallet application.

In accordance with some embodiments, the authorization is received froma user via a user input at the electronic device. For example, asillustrated in FIG. 18C, after receiving the request, the electronicdevice displays a user interface of the electronic wallet applicationthat includes an affordance 1832. To provide authorization, the useractivates affordance 1832. For another example, the user may provide afingerprint at a fingerprint sensor of the electronic device, whereinthe fingerprint corresponds to fingerprint information on the devicethat can provide authorization. In some examples, the user interfacethat requests authorization from the user also includes a visualrepresentation 1830 of the payment card to be added. This allows theuser to quickly understand which payment account will be added ifauthorization is provided. In accordance with some embodiments, theauthorization is received from the financial institution. For example,the financial institution may transmit an authorization via the Internetto the electronic device.

In accordance with some embodiments, as illustrated in FIG. 18A, priorto storing information associated with the payment account that isprovided by the third-party application to the secured area of thedevice, the electronic device receives user input including user logininformation for the financial application. For example, the user logsinto the financial application using credentials such as a login andpassword.

In accordance with some embodiments, as illustrated in FIG. 18B, theuser interface for the financial application includes displayed detailsabout the payment account associated with the financial institution(e.g., a portion of the account number 1804, the name of the accountholder 1806, and/or card background art).

As illustrated in FIG. 18D, in accordance with some embodiments, theelectronic device displays a user interface for the first-partyelectronic wallet application, the displayed user interface for thefirst-party electronic wallet application including the details 1830about the payment account associated with the financial institution(e.g., after the payment account is added to the electronic wallet, theuser interface of the electronic wallet application includes some of thesame details as the user interface for the financial application). Forexample, the user interface for the first-party electronic walletapplication may include a portion of the account number, the name of theaccount holder, and/or card background art.

In accordance with some embodiments, the electronic device accesses thestored information associated with the payment account from the securedarea of the device. The electronic device provides the accessedinformation associated with the payment account to a purchasingapplication (e.g., a third-party application or web browser running onthe device that the user can use to make purchases) that is restrictedfrom accessing the secured area of the device. In some embodiments, thepurchasing application engages in a payment transaction using theinformation associated with the payment account. In some embodiments,engaging in the payment transaction includes routing information to oneor more financial institutions to verify payment credentials and/orreceive authorization to complete the transaction.

In accordance with some embodiments, as illustrated in FIG. 18E, an NFCpayment can be made using the payment account after the payment accounthas been added to the electronic wallet of the electronic device. Theuser places the electronic device into a field 612 of a contactlesspayment terminal 610, wherein the electronic device includes one or morewireless communication elements. The electronic device accesses thestored information associated with the payment account from the securedarea of the device. The electronic device transmits, using the one ormore wireless communication elements, the information associated withthe payment account to the payment terminal 610 that is proximate to theelectronic device. The information associated with the payment accountenables the payment terminal 610 to engage in a payment transaction. Insome embodiments, engaging in the payment transaction includes routinginformation to one or more financial institutions to verify paymentcredentials and/or receive authorization to complete the transaction.For example, the payment account information may be transmitted to acontactless payment terminal using NFC.

In accordance with some embodiments, the electronic device provides thefinancial application access (e.g., write only access) to a portion ofthe secured area of the device. In some examples, the electronic walletapplication acts as an intermediary to achieve the access to the portionof the secured area of the device. In other examples, the financialapplication can directly access the portion of the secured area of thedevice. This allows the financial application to write the informationassociated with the payment account into the secured area of the device.

In accordance with some embodiments, the electronic device writes theinformation associated with the payment account into the secured area ofthe device. In some examples, this allows the payment account to be usedby the electronic device for mobile payments, such as web payments orNFC payments (e.g., without requiring the user to provide the accountdetails).

In accordance with some embodiments, in response to writing theinformation associated with the payment account into the secured area ofthe device, the electronic device provides an indication (e.g., 1840; avisual, audio, or haptic alert) that the payment account has been linkedto the device.

In accordance with some embodiments, the electronic wallet of theelectronic device includes one or more different payment accountsassociated with a user of the electronic device. In some embodiments,when the device detects that the user has placed the device into thefield of the contactless payment terminal, the device transmits anidentifier, such as a PAN, of a selected payment account (from among theone or more different payment accounts) to the contactless paymentterminal.

FIG. 19 is a flow diagram illustrating a method for linking a paymentaccount to an electronic device, in accordance with some embodiments.Method 1900 is performed at a device (e.g., 100, 300, 500) a display.Some operations in method 1900 may be combined, the order of someoperations may be changed, and some operations may be omitted.

As described below, method 1900 provides an intuitive way for linking apayment account to an electronic device, in accordance with someembodiments. The method reduces the cognitive burden on a user forlinking a payment account to the electronic device, thereby creating amore efficient human-machine interface. For battery-operated computingdevices, linking payment accounts faster and more efficiently conservespower and increases the time between battery charges.

At block 1902, the electronic device displays a user interface for afinancial application that is one of a plurality of applications on theelectronic device. The financial application is a third-partyapplication that is associated with a financial institution, and thefinancial application is restricted from accessing a secured area of thedevice that is accessible by a first-party electronic walletapplication. For example, the financial application has less access tothe secured area as compared to the electronic wallet application. Foranother example, the financial application only has write access to thesecured area.

At block 1904, while displaying the user interface for the financialapplication, the electronic device receives a request to add a paymentaccount associated with the financial institution to the electronicwallet. For example, the device detects activation of affordance 1822.

At block 1906, in response to receiving the request to add the paymentaccount associated with the financial institution to the electronicwallet and in accordance with a determination that addition of thepayment account to the electronic wallet has been authorized (e.g., thedevice detects activation of affordance 1832 authorizing addition of thepayment account to the wallet), the electronic device stores informationassociated with the payment account that is provided by the third-partyapplication to the secured area of the device that is accessible by thefirst-party electronic wallet application.

In accordance with some embodiments, the authorization is received froma user via a user input at the electronic device. For example, the useractivates affordance 1832 to authorize the addition of the paymentaccount to the electronic wallet. In accordance with some embodiments,the authorization is received from the financial institution. Forexample, the electronic device receives a validated token from thefinancial institution.

In accordance with some embodiments, prior to storing informationassociated with the payment account that is provided by the third-partyapplication to the secured area of the device, the electronic devicereceives user input including user login information (e.g., the contentof fields 1812 and 1814) for the financial application.

In accordance with some embodiments, the user interface for thefinancial application includes displayed details (e.g., 1806, 1804)about the payment account associated with the financial institution.

In accordance with some embodiments, the electronic device displays auser interface for the first-party electronic wallet application, thedisplayed user interface for the first-party electronic walletapplication including the details (e.g., 1830) about the payment accountassociated with the financial institution.

In accordance with some embodiments, the electronic device accesses thestored information associated with the payment account from the securedarea of the device. The electronic device provides the accessedinformation associated with the payment account to a purchasingapplication that is restricted from accessing the secured area of thedevice. In some embodiments, the purchasing application engages in apayment transaction using the information associated with the paymentaccount. In some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction.

In accordance with some embodiments, the electronic device includes oneor more wireless communication elements. As illustrated in FIG. 18E, thedevice is placed into a field (e.g., 612) of a payment terminal (e.g.,610). The electronic device accesses the stored information associatedwith the payment account from the secured area of the device. Theelectronic device transmits, using the one or more wirelesscommunication elements, the information associated with the paymentaccount to the payment terminal (e.g., 610) that is proximate to theelectronic device. The information associated with the payment accountenables the payment terminal (e.g., 610) to engage in a paymenttransaction. In some embodiments, engaging in the payment transactionincludes routing information to one or more financial institutions toverify payment credentials and/or receive authorization to complete thetransaction. For example, the payment account information is transmittedto a contactless payment terminal using NFC.

In accordance with some embodiments, the electronic device provides thefinancial application access (e.g., write only access) to a portion ofthe secured area of the device. In some examples, the electronic walletapplication acts as an intermediary to achieve the access to the portionof the secured area of the device.

In accordance with some embodiments, the electronic device writes theinformation associated with the payment account into the secured area ofthe device. In some examples, this allows the payment account to be usedby the electronic device for mobile payments, such as web payments orNFC payments (e.g., without requiring the user to provide the accountdetails).

In accordance with some embodiments, in response to writing theinformation associated with the payment account into the secured area ofthe device, the electronic device provides an indication (e.g., 1840; avisual, audio, or haptic alert) that the payment account has been linkedto the device.

In accordance with some embodiments, the electronic wallet of theelectronic device includes one or more different payment accountsassociated with a user of the electronic device. In some embodiments,when the device detects that the user has placed the device into thefield of the contactless payment terminal, the device transmits anidentifier, such as a PAN, of a selected payment account (from among theone or more different payment accounts) to the contactless paymentterminal.

Note that details of the processes described above with respect tomethod 1900 (e.g., FIG. 19) are also applicable in an analogous mannerto the methods described above. For example, methods 700, 900, 1100,1300, 1500, and 1700 may include one or more of the characteristics ofthe various methods described above with reference to method 1900. Forexample, the electronic wallet, payment accounts, loyalty accounts,affordances, and inputs of methods 700, 900, 1100, 1300, 1500, and 1700optionally have one or more of the characteristics of the electronicwallet, payment accounts, loyalty accounts, affordances, and inputs ofthe electronic device described in method 1900. For brevity, thesedetails are not repeated.

In accordance with some embodiments, FIG. 20 shows an exemplaryfunctional block diagram of an electronic device 2000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2000 are configured to perform the techniques described above.The functional blocks of the device 2000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 20 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 20, an electronic device 2000 includes a display unit2002 configured to display a graphic user interface, one or morewireless communication elements 2004, and a processing unit 2006 coupledto the display unit 2002 and the one or more wireless communicationelements 2004. In some embodiments, the processing unit 2006 includes atransmitting unit 2010, a receiving unit 2012, a display enabling unit2014, and optionally, a determining unit 2016, a forgoing unit 2018, anda linking unit 2020.

The processing unit 2006 is configured to transmit (e.g., using thetransmitting unit 2010), using the one or more wireless communicationelements 2004, payment account information to a payment terminal that isproximate to the electronic device, where the payment accountinformation enables the payment terminal to engage in a paymenttransaction; subsequent to engaging in the payment transaction with thepayment terminal, receive (e.g., using the receiving unit 2012), from aremote source, loyalty information of a loyalty account; enable display(e.g., using the display enabling unit 2014) of, on the display unit2002, a linking affordance; receive user input corresponding to anactivation of the linking affordance; and in response to receiving theuser input, enable display (e.g., using the display enabling unit 2014)of, on the display unit 2002, a user interface for linking the loyaltyaccount to the electronic device.

In some embodiments, the processing unit 2006 is further configured to,prior to enabling display of the linking affordance, determine (e.g.,using the determining unit 2016) that the loyalty account is not linkedto the electronic device.

In some embodiments, the loyalty information includes an identifier thatis particular to the loyalty account.

In some embodiments, the payment transaction is a payment transactionbetween the payment account and a merchant and the user interface forlinking the loyalty account to the electronic device includes one ormore pre-populated fields, where the one or more pre-populated fieldsare populated with information associated with setting up a new loyaltyaccount associated the merchant.

In some embodiments, the user interface for linking the loyalty accountto the electronic device includes a cancellation affordance, theprocessing unit 2006 further configured to receive (e.g., using thereceiving unit 2012) user input corresponding to an activation of thecancellation affordance and in response to receiving the user inputcorresponding to the activation of the cancellation affordance, forgo(e.g., using the forgoing unit 2018) transmitting content of the one ormore pre-populated fields.

In some embodiments, the user interface for linking the loyalty accountto the electronic device includes a confirmation affordance to link theloyalty account to the electronic device, the processing unit 2006further configured to receive (e.g., using the receiving unit 2012)activation of the confirmation affordance and in response to receivingactivation of the confirmation affordance, link (e.g., using the linkingunit 2020) the loyalty account to the electronic device.

In some embodiments, the processing unit 2006 is further configured to,subsequent to activation of the linking affordance, receive (e.g., usingthe receiving unit 2012) an input corresponding to election of a settingassociated with the loyalty account, where the setting identifies astatus for providing loyalty account information of the loyalty accountduring a subsequent transaction in the absence of input specifying adifferent loyalty account before the device receives authorization toproceed with a transaction using the device.

In some embodiments, the processing unit 2006 is further configured to,prior to receiving the loyalty information, receive (e.g., using thereceiving unit 2012) from the payment terminal, via the one or morewireless communication elements 2004, a request for loyalty accountinformation of a first type of loyalty account and, in response toreceiving the request for the loyalty account information of the firsttype of loyalty account, transmit (e.g., using the transmitting unit2010) to the payment terminal, via the one or more wirelesscommunication elements 2004, information indicating that the first typeof loyalty account is not linked to the electronic device.

In some embodiments, the payment transaction was conducted using apayment account of an electronic wallet of the electronic device.

In some embodiments, the electronic wallet includes payment accountinformation for a second payment account associated with a user of theelectronic device, where the second payment account is distinct from thepayment account.

The operations described above with reference to FIG. 7 are, optionally,implemented by components depicted in FIGS. 1A-1B or FIG. 20. Forexample, transmitting operation 702; receiving operations 704, 708, and710; and displaying operation 706 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 21 shows an exemplaryfunctional block diagram of an electronic device 2100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2100 are configured to perform the techniques described above.The functional blocks of the device 2100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 21 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 21, an electronic device 2100 includes one or morewireless communication elements 2102 and one or more input devices 2104,and a processing unit 2106 coupled to the one or more wirelesscommunication elements 2102 and the one or more input devices 2104. Insome embodiments, the processing unit 2106 includes a receiving unit2110, a determining unit 2112, a transmitting unit 2114, a forgoing unit2116, and optionally, a providing unit 2118, a detecting unit 2120, anda proceeding unit 2122.

The processing unit 2106 is configured to receive (e.g., using thereceiving unit 2110), via the one or more wireless communicationelements 2102, from a contactless payment terminal that is proximate tothe electronic device, a request for loyalty account information for apayment transaction for which authorization to proceed has been providedvia the one or more input devices 2104 of the electronic device; and inresponse to receiving the request for loyalty account information:determine (e.g., using the determining unit 2112) whether aloyalty-sharing condition is met; in accordance with a determinationthat the loyalty-sharing condition is met, transmit (e.g., using thetransmitting unit 2114) loyalty account information of a loyalty accountto the contactless payment terminal via the one or more wirelesscommunication elements 2102; and in accordance with a determination thatthe loyalty-sharing condition is not met, forgo (e.g., using theforgoing unit 2116) transmitting loyalty account information of theloyalty account to the contactless payment terminal.

In some embodiments, the processing unit 2106 is further configured to,prior to transmitting loyalty account information of the loyaltyaccount, determine (e.g., using the determining unit 2112) thatauthorization to proceed with the payment transaction is provided, wheretransmitting loyalty account information of a loyalty account to thecontactless payment terminal via the one or more wireless communicationelements 2102 occurs without requiring separate authorization.

In some embodiments, the processing unit 2106 is further configured to,in accordance with a determination that the loyalty-sharing condition isnot met and a loyalty sharing permission regarding user instruction toprovide the loyalty account information in the absence of inputspecifying a different payment account before the device receivesauthorization to proceed with a payment transaction using the device isnot stored on the electronic device, provide (e.g., using the providingunit 2118) an alert requesting confirmation to provide the loyaltyaccount information to the contactless payment terminal.

In some embodiments, the one or more input devices 2104 of theelectronic device include a fingerprint sensor, the processing unit 2106further configured to, in accordance with the determination that theloyalty-sharing condition is not met and while detecting a fingerprinton the fingerprint sensor: provide (e.g., using the providing unit 2118)a notification requesting authorization to transmit loyalty accountinformation of the loyalty account to the contactless payment terminal;detect (e.g., using the detecting unit 2120), via the one or morewireless communication elements 2102, that the device has been removedfrom a field of the contactless payment terminal and replaced into thefield of the contactless payment terminal; and in response to detectingthat the device has been replaced into the field of the contactlesspayment terminal, determine (e.g., using the determining unit 2112) thatthe fingerprint is consistent with an enrolled fingerprint that isenabled to authorize transactions; and in response to determining thatthe fingerprint is consistent with an enrolled fingerprint that isenabled to authorize transactions, transmit (e.g., using thetransmitting unit 2114) loyalty account information of the loyaltyaccount to the contactless payment terminal.

In some embodiments, the one or more input devices 2104 of theelectronic device include a fingerprint sensor, the processing unit 2106further configured to, in accordance with the determination that theloyalty-sharing condition is not met and while detecting a fingerprinton the fingerprint sensor: provide (e.g., using the providing unit 2118)a notification requesting authorization to transmit loyalty accountinformation of the loyalty account to the contactless payment terminal;receive (e.g., using the receiving unit 2110) user input selecting asecond loyalty account different from the loyalty account; detect (e.g.,using the detecting unit 2120), via the one or more wirelesscommunication elements 2102, that the device has been removed from afield of the contactless payment terminal and replaced into the field ofthe contactless payment terminal; in response to detecting that thedevice has been replaced into the field of the contactless paymentterminal, determine (e.g., using the determining unit 2112) that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize transactions; and in response to determining that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize transactions, transmit (e.g., using the transmitting unit2114) loyalty account information of the second loyalty account to thecontactless payment terminal.

In some embodiments, the one or more input devices 2104 of theelectronic device include a fingerprint sensor, the processing unit 2106further configured to, in accordance with the determination that theloyalty-sharing condition is not met and while detecting a fingerprinton the fingerprint sensor: provide (e.g., using the providing unit 2118)a notification requesting authorization to transmit loyalty accountinformation of the loyalty account to the contactless payment terminal;receive (e.g., using the receiving unit 2110) user input declining touse the loyalty account; detect (e.g., using the detecting unit 2120),via the one or more wireless communication elements 2102, that thedevice has been removed from a field of the contactless payment terminaland replaced into the field of the contactless payment terminal; inresponse to detecting that the device has been replaced into the fieldof the contactless payment terminal, determine (e.g., using thedetermining unit 2112) that the fingerprint is consistent with anenrolled fingerprint that is enabled to authorize transactions; and inresponse to determining that the fingerprint is consistent with anenrolled fingerprint that is enabled to authorize transactions, proceed(e.g., using the proceeding unit 2122) with the payment transactionwithout transmitting the loyalty account information of the loyaltyaccount to the contactless payment terminal.

In some embodiments, the processing unit 2106 is further configured to,in accordance with a determination that the loyalty-sharing condition isnot met and a loyalty sharing permission stored on the electronic deviceindicates user instruction to not provide the loyalty accountinformation in the absence of input specifying a different paymentaccount before the device receives authorization to proceed with apayment transaction using the device, proceed (e.g., using theproceeding unit 2122) with the payment transaction using a paymentaccount without prompting for confirmation.

In some embodiments, the loyalty-sharing condition includes a conditionthat is met when the electronic device has previously been authorized toprovide the loyalty account information of the loyalty account to thecontactless payment terminal.

In some embodiments, the loyalty-sharing condition includes a conditionthat is met when the electronic device has previously been authorized toprovide the loyalty account information of the loyalty account to adifferent contactless payment terminal in a group of contactless paymentterminals that includes the contactless payment terminal.

In some embodiments, the loyalty-sharing condition includes a conditionthat is met when the electronic device has previously been authorized toprovide the loyalty account information of the loyalty account to one ormore contactless payment terminals within a predetermined geographicalregion in which the contactless payment terminal is located.

In some embodiments, the processing unit 2106 is further configured to,prior to receiving the request for loyalty account information, detect(e.g., using the detecting unit 2120) a field of the contactless paymentterminal and prior to detecting the field of the contactless paymentterminal, receive (e.g., using the receiving unit 2110), via the one ormore input devices 2104 of the electronic device, the authorization toproceed.

In some embodiments, the processing unit 2106 is further configured to:prior to receiving the request for loyalty account information, detect(e.g., using the detecting unit 2120) a field of the contactless paymentterminal; and while detecting the field of the contactless paymentterminal, receive (e.g., using the receiving unit 2110), via the one ormore input devices 2104 of the electronic device, the authorization toproceed.

In some embodiments, the processing unit 2106 is further configured to,after transmitting loyalty account information of a loyalty account tothe contactless payment terminal via the one or more wirelesscommunication elements 2102 for a predefined number of loyalty accounts,receive (e.g., using the receiving unit 2110) a request for loyaltyaccount information of a second loyalty account from the contactlesspayment; and in response to receiving the request for loyalty accountinformation of the second loyalty account from the contactless payment,forgo (e.g., using the forgoing unit 2116) transmitting loyalty accountinformation of the second loyalty account to the contactless payment forthe payment transaction.

In some embodiments, the one or more input devices 2104 comprises afingerprint sensor and where the authorization was provided inaccordance with: detecting (e.g., using the detecting unit 2120) arespective fingerprint on the fingerprint sensor of the electronicdevice; and in response to detecting the respective fingerprint on thefingerprint sensor, determining (e.g., using the determining unit 2112)that the fingerprint is consistent with an enrolled fingerprint that isenabled to authorize payment transactions.

In some embodiments, the one or more input devices 2104 comprises atouch-sensitive surface and where the authorization was provided inaccordance with receiving (e.g., using the receiving unit 2110) apasscode via the touch-sensitive surface of the electronic device and,in response to receiving the passcode, determining (e.g., using thedetermining unit 2112) that the passcode is consistent with an enrolledpasscode that is enabled to authorize payment transactions.

In some embodiments, the payment transaction is conducted using apayment account of an electronic wallet of the electronic device.

In some embodiments, an electronic wallet of the electronic deviceincludes loyalty account information for one or more different loyaltyaccounts associated with a user of the electronic device, the one ormore different loyalty accounts being different from the loyalty accountused for the payment transaction.

In some embodiments, the processing unit 2106 is further configured totransmit (e.g., using the transmitting unit 2114), using the one or morewireless communication elements 2102, payment account information to thecontactless payment terminal, where the payment account informationenables the contactless payment terminal to engage in the paymenttransaction.

The operations described above with reference to FIG. 9 are, optionally,implemented by components depicted in FIGS. 1A-1B or FIG. 21. Forexample, receiving operation 902; determining operation 904,transmitting operation 906, and forgoing operation 908 may beimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 22 shows an exemplaryfunctional block diagram of an electronic device 2200 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2200 are configured to perform the techniques described above.The functional blocks of the device 2200 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 22 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 22, an electronic device 2200 includes one or morewireless communication elements 2202 and a display unit 2204 configuredto display a graphic user interface, and a processing unit 2206 coupledto the one or more wireless communication elements 2202 and the displayunit 2204. In some embodiments, the processing unit 2206 includes areceiving unit 2210 and a display enabling unit 2212, and optionally, aconducting unit 2214, a detecting unit 2216, a determining unit 2218,and a transmitting unit 2220.

The processing unit 2206 is configured to receive (e.g., using thereceiving unit 2210), via the one or more wireless communicationelements 2202, information about a payment transaction for which aloyalty account is available to be used; in response to receiving theinformation about the payment transaction, concurrently enable display(e.g., using display enabling unit 2212) of, on the display unit 2204 anindication of a payment account for the payment transaction and anindication of the loyalty account for the payment transaction.

In some embodiments, the processing unit 2206 is further configured to,subsequent to concurrently enabling display of, on the display unit2204, the indication of the payment account for the payment transactionand the indication of the loyalty account for the payment transaction,conduct (e.g., using conducting unit 2214) the payment transaction usingthe payment account of an electronic wallet of the electronic device.

In some embodiments, the processing unit 2206 is further configured to,prior to concurrently enabling display of, on the display unit 2204, theindication of the payment account for the payment transaction and theindication of the loyalty account for the payment transaction, conduct(e.g., using conducting unit 2214) the payment transaction using thepayment account of an electronic wallet of the electronic device.

In some embodiments, the processing unit 2206 is further configured to,prior to receiving, via the one or more wireless communication elements2202, information about the payment transaction for which a loyaltyaccount is available, detect (e.g., using detecting unit 2216) a fieldof a contactless payment terminal and determine (e.g., using determiningunit 2218) that the electronic device is in a location in which theloyalty account can be used.

In some embodiments, the processing unit 2206 is further configured toprior to receiving, via the one or more wireless communication elements2202, information about the payment transaction for which a loyaltyaccount is available, receive (e.g., using the receiving unit 2210), viathe one or more wireless communication elements 2202, information fromthe contactless payment terminal indicating that loyalty accountinformation has been entered at the payment transaction terminal.

In some embodiments, the processing unit 2206 is further configured to,prior to receiving, via the one or more wireless communication elements2202, information about the payment transaction for which a loyaltyaccount is available, receive (e.g., using the receiving unit 2210), viathe one or more wireless communication elements 2202, information fromthe contactless payment terminal indicating that the loyalty accountwould be accepted.

In some embodiments, the payment transaction is conducted using apayment account of an electronic wallet of the electronic device.

In some embodiments, an electronic wallet of the electronic deviceincludes loyalty account information for one or more different loyaltyaccounts associated with a user of the electronic device, the one ormore different loyalty accounts being different from the loyalty accountused for the payment transaction.

In some embodiments, an electronic wallet of the electronic deviceincludes loyalty account information for the loyalty account and paymentaccount information for the payment account.

In some embodiments, the payment account is a default payment account.

In some embodiments, concurrently enabling display (e.g., using displayenabling unit 2212) of, on the display unit 2204, the indication of thepayment account for the payment transaction and the indication of theloyalty account for the payment transaction occurs prior to receivingauthorization to proceed with the payment transaction.

In some embodiments, the processing unit 2206 is further configured totransmit (e.g., using transmitting unit 2220), using the one or morewireless communication elements, 2202 payment account information of thepayment account to the contactless payment terminal, where the paymentaccount information enables the contactless payment terminal to engagein the payment transaction.

In some embodiments, the processing unit 2206 is further configured to,subsequent to transmitting payment account information of the paymentaccount, transmit (e.g., using transmitting unit 2220), using the one ormore wireless communication elements 2202, loyalty account informationof the loyalty account to the contactless payment terminal.

In some embodiments, the processing unit 2206 is further configured to,prior to transmitting payment account information of the paymentaccount, transmit (e.g., using transmitting unit 2220), using the one ormore wireless communication elements 2202, loyalty account informationof the loyalty account to the contactless payment terminal.

In some embodiments, the processing unit 2206 is further configured toreceive (e.g., using the receiving unit 2210), using the one or morewireless communication elements 2202, confirmation of acceptance ofpayment account information of the payment account and loyalty accountinformation of the loyalty account and in response to receivingconfirmation of acceptance of payment account information, enabledisplay (e.g., using display enabling unit 2212) of, on the display unit2204, a confirmation of acceptance of payment account information of thepayment account and loyalty account information of the loyalty account.

In some embodiments, the processing unit 2206 is further configured todetermine (e.g., using determining unit 2218) that the contactlesspayment terminal has not approved the loyalty account and in response todetermining that the contactless payment terminal has not approved theloyalty account, enable display (e.g., using display enabling unit 2212)of the indication of the payment account and forgoing display of theindication of the loyalty account.

In some embodiments, the processing unit 2206 is further configured to,prior to transmitting the payment account to the contactless paymentterminal, enable display (e.g., using display enabling unit 2212) of, onthe display unit 2204, a description of a prospective benefit of using aloyalty program associated with the loyalty account.

In some embodiments, the processing unit 2206 is further configured to,subsequent to transmitting the payment account to the contactlesspayment terminal, enable display (e.g., using display enabling unit2212) of, on the display unit 2204, a description of savings generatedby using a loyalty program associated with the loyalty account.

In some embodiments, the processing unit 2206 is further configured to,subsequent to transmitting the payment account to the contactlesspayment terminal, enable display (e.g., using display enabling unit2212) of, on the display unit 2204, an indication of progress toward anobjective associated with the loyalty account.

The operations described above with reference to FIG. 11 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.22. For example, receiving operation 1102 and displaying operation 1104may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 23 shows an exemplaryfunctional block diagram of an electronic device 2300 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2300 are configured to perform the techniques described above.The functional blocks of the device 2300 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 23 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 23, an electronic device 2300 includes one or morewireless communication elements 2302 and a processing unit 2304 coupledto the one or more wireless communication elements 2302. In someembodiments, the processing unit 2304 includes a receiving unit 2310, adetermining unit 2312, a proceeding unit 2314, a forgoing unit 2316, andoptionally, a requesting unit 2318, and a providing unit 2320.

The processing unit 2304 is configured to receive (e.g., using thereceiving unit 2310), from a contactless payment terminal via the one ormore wireless communication elements 2302, a request associated with apayment transaction; determine (e.g., using the determining unit 2312)whether the request comprises a request for payment using a particularpayment account type; in accordance with a determination that therequest does not comprise the request for payment using the particularpayment account type, proceed (e.g., using the proceeding unit 2314)with the payment transaction using a default payment account; and inaccordance with a determination that the request comprises the requestfor payment using the particular payment account type, determine (e.g.,using the determining unit 2312) whether a payment account selectioncondition is met and in accordance with a determination that the paymentaccount selection condition is not met, forgo (e.g., using the forgoingunit 2316) proceeding with the payment transaction using a paymentaccount of the particular payment account type.

In some embodiments, the processing unit 2304 is further configured to,in accordance with the determination that the request comprises therequest for payment using the particular payment account type and inaccordance with a determination that the payment account selectioncondition is met, proceed (e.g., using the proceeding unit 2314) withthe payment transaction using the payment account of the particularpayment account type.

In some embodiments, the processing unit 2304 is further configured to,in accordance with the determination that the request comprises therequest for payment using the particular payment account type and inaccordance with the determination that the payment account selectioncondition is not met, request (e.g., using the requesting unit 2318)authorization from user to proceed with the payment transaction usingthe payment account of the particular payment account type.

In some embodiments, the processing unit 2304 is further configured to,in accordance with the determination that the request comprises therequest for payment using the particular payment account type and inaccordance with the determination that the payment account selectioncondition is not met, receive (e.g., using the receiving unit 2310) auser input, and in response to receiving the user input, provide (e.g.,using the providing unit 2320) an indication that a second paymentaccount different from the payment account of the particular paymentaccount type will be used for proceeding with the payment transaction.

In some embodiments, the second payment account is the default paymentaccount.

In some embodiments, the payment account selection condition is not metwhen the contactless payment terminal is of a first type, and the devicehas not previously received approval from a user to use the particularpayment account of the particular payment account type at contactlesspayment terminals of the first type in the absence of input specifying adifferent payment account before the device receives authorization toproceed with a payment transaction using the device.

In some embodiments, the payment account selection condition includes acriterion that is met when the device receives a verified request fromthe contactless payment terminal.

In some embodiments, the payment account selection condition includes acriterion that is met when the device has previously proceeded with oneor more payment transactions at the contactless payment terminal usingthe payment account of the particular payment account type.

In some embodiments, the payment account selection condition includes acriterion that is met when the device has previously proceeded with oneor more payment transactions at a location that is associated with thecontactless payment terminal using the payment account of the particularpayment account type.

In some embodiments, the payment account selection condition includes acriterion that is met when the device has previously proceeded with oneor more payment transactions at the contactless payment terminal usingthe payment account of the particular payment account type.

In some embodiments, the processing unit 2304 is further configured to,prior to receiving the request associated with the payment transaction:receive (e.g., using the receiving unit 2310) payment accountinformation for the particular payment account and receive (e.g., usingthe receiving unit 2310) user input indicating whether the particularpayment account should be used at contactless payment terminals of afirst type in the absence of input specifying a different paymentaccount before the device receives authorization to proceed with apayment transaction using the device.

In some embodiments, an electronic wallet of the electronic deviceincludes one or more different payment accounts associated with a userof the electronic device, the one or more different payment accountsbeing different from the particular payment account.

The operations described above with reference to FIG. 13 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.23. For example, receiving operation 1302, determining operations 1304and 1310, proceeding operation 1306, and forgoing operation 1312 may beimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 24 shows an exemplaryfunctional block diagram of an electronic device 2400 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2400 are configured to perform the techniques described above.The functional blocks of the device 2400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 24 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 24, an electronic device 2400 includes a locationsensor 2402, a display unit 2404 configured to display a graphic userinterface, optionally, a short range communication radio 2406, and aprocessing unit 2408 coupled to the location sensor 2404, the displayunit 2404, and, optionally, the short range communication radio 2406. Insome embodiments, the processing unit 2408 includes a detecting unit2410, a determining unit 2412, a display enabling unit 2414, a forgoingunit 2416, and optionally, a receiving unit 2418, a preparing unit 2420,and a providing unit 2422.

The processing unit 2408 is configured to detect (e.g., using thedetecting unit 2410), using the location sensor, that a current locationis associated with prompting for use of a particular payment account; inresponse to detecting that the current location is associated withprompting for use of the particular payment account, determine (e.g.,using the determining unit 2412) whether the electronic device haspreviously received an indication of a user preference associated withusing the particular payment account at the current location; inaccordance with a determination that the device has previously receivedan indication of the user preference associated with using theparticular payment account at the current location, enable display(e.g., using the display enabling unit 2414) of, on the display unit2404, a visual indication that the particular payment account isavailable for use at the location; and in accordance with adetermination that the device has not previously received an indicationof the user preference associated with using the particular paymentaccount at the current location, forgo (e.g., using the forgoing unit2416) enabling display of, on the display unit 2404, the visualindication that the particular payment account is available for use atthe location.

In some embodiments, enabling display (e.g., using the display enablingunit 2414) of, on the display unit 2404, the visual indication comprisesenabling display of a visual indication that the particular paymentaccount will be used for a payment transaction conducted at the currentlocation in the absence of input specifying a different payment accountbefore the device receives authorization to proceed with a paymenttransaction using the device.

In some embodiments, enabling display of, on the display unit 2404, thevisual indication comprises enabling display of a visual indicationrecommending that the particular payment account be used for a paymenttransaction conducted at the current location, the processing unit 2408further configured to receive (e.g., using the receiving unit 2418) userinput accepting the recommendation and prepare (e.g., using thepreparing unit 2420) the particular payment account for use at acontactless payment terminal at the current location.

In some embodiments, the current location is based on one or more ofreceived short-range communication signals and received GPS signals.

In some embodiments, the electronic device includes a short-rangecommunication radio 2406, the processing unit 2408 further configuredto, subsequent to determining whether the electronic device haspreviously received an indication of a user preference: detect (e.g.,using detecting unit 2410), by the short-range communication radio 2406,presence of a field generated by a contactless payment terminal whileauthorization to proceed with the payment transaction has not beenprovided; in response to detecting presence of the field generated bythe contactless payment terminal authorization to proceed with thepayment transaction has not been provided, provide (e.g., using theproviding unit 2422) a prompt to authorize payment; after providing theprompt, receive (e.g., using the receiving unit 2418) user inputselecting a second payment account for use in a payment transaction atthe current location; and in response to receiving the user inputselecting the second payment account, prepare (e.g., using the preparingunit 2420) to use the second payment account in the payment transaction.

In some embodiments, an electronic wallet of the electronic deviceincludes one or more different payment accounts associated with a userof the electronic device, the one or more different payment accountsbeing different from the particular payment account.

The operations described above with reference to FIG. 15 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.24. For example, detecting operation 1502, determining operation 1506,displaying operation 1508, and forgoing operation 1510 may beimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 25 shows an exemplaryfunctional block diagram of an electronic device 2500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2500 are configured to perform the techniques described above.The functional blocks of the device 2500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 25 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 25, an electronic device 2500 includes a display unit2502 configured to display a user graphic interface, one or more inputdevices 2504, optionally, a camera sensor 2506, a touch-sensitivesurface unit 2520, and a short range communication radio 2522, and aprocessing unit 2508 coupled to the display unit 2502, the one or moreinput devices 2504, and optionally the camera sensor 2506, thetouch-sensitive display 2520, and the short range communication radio2522. In some embodiments, the processing unit 2508 includes a receivingunit 2510, a determining unit 2512, a display enabling unit 2514, andoptionally a detecting unit 2516 and a forgoing unit 2518.

In some embodiments, the processing unit 2508 is configured to receive(e.g., using the receiving unit 2510), via the one or more input devices2504, a request to link a payment card with the electronic device, therequest comprising account information; in response to receiving therequest via the one or more input devices 2504: determine (e.g., usingthe determining unit 2512) whether the payment card is associated withmultiple payment accounts; in accordance with a determination that thepayment card is associated with multiple payment accounts, enabledisplay (e.g., using the display enabling unit 2514) of, on the displayunit 2502, a payment account interface for the payment card that enablesuser selection among multiple payment accounts of the payment card; andin accordance with a determination that the payment card is notassociated with multiple payment accounts, enable display (e.g., usingthe display enabling unit 2514) of, on the display unit 2502, a paymentaccount interface for the payment card that does not enable userselection among multiple payment accounts of the payment card.

In some embodiments, the electronic device includes a camera sensor 2506and where the request to link the payment card with the electronicdevice is based on an image of the payment card, the image captured bythe camera sensor 2506 of the electronic device.

In some embodiments, the payment card is associated with multiplepayment accounts and where the payment account interface for the paymentcard includes a plurality of affordances for the multiple paymentaccounts associated with the payment card.

In some embodiments, the plurality of affordance are grouped together toindicate that they relate to a single payment card.

In some embodiments, the plurality of affordances are displayed in arow.

In some embodiments, the electronic device includes a touch-sensitivesurface unit 2520, the processing unit 2508 further configured toreceive (e.g., using the receiving unit 2510), at the touch-sensitivesurface unit 2520, a vertical swipe input; and in response to receivingthe vertical swipe input, enable display (e.g., using the displayenabling unit 2514) of a plurality of affordances, where a first cardaffordance of the plurality of affordances represents a first group ofmultiple payment accounts and a second card affordance of the pluralityof affordances represents a second group of multiple payment accountsdistinct from the first group.

In some embodiments, the processing unit 2508 is further configured toreceive (e.g., using the receiving unit 2510) user input activating thefirst card affordance; and in response to receiving the user inputactivating the first card affordance, enable display (e.g., using thedisplay enabling unit 2514) of a first set of account affordancesassociated with the first group of multiple payment accounts.

In some embodiments, the displayed plurality of affordances for themultiple payment accounts of the payment card are based on a currentlocation of the electronic device.

In some embodiments, the payment card is associated with multiplepayment accounts and where the electronic device includes a short-rangecommunication radio 2522, the processing unit 2508 further configured todetect (e.g., using the detecting unit 2516), by the short-rangecommunication radio 2522, presence of a field generated by a contactlesspayment terminal; in response to detecting presence of the fieldgenerated by the contactless payment terminal, determine (e.g., usingthe determining unit 2516) whether the contactless payment terminalsupports a first type of payment account; and in accordance with adetermination the contactless payment terminal does not support thefirst type of payment account, forgo (e.g., using the forgoing unit2518) providing an option to select the payment account of the paymentcard of the first type.

In some embodiments, the payment card is associated with multiplepayment accounts and where the payment account interface for the paymentcard includes a plurality of affordances for the multiple paymentaccounts associated with the payment card, the plurality of affordancesdisplayed based on a priority order.

The operations described above with reference to FIG. 17 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.25. For example, receiving operation 1702, determining operation 1706,and displaying operations 1708 and 1710 may be implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 26 shows an exemplaryfunctional block diagram of an electronic device 2600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 2600 are configured to perform the techniques described above.The functional blocks of the device 2600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 26 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 26, an electronic device 2600 includes a display unit2602, optionally, one or more wireless communication elements 2604, anda processing unit 2606 coupled to the display unit 2602 and, optionally,the one or more wireless communication elements 2604. In someembodiments, the processing unit 2606 includes a display enabling unit2610, a receiving unit 2612, a storing unit 2614, and optionally, anaccessing unit 2616, a providing unit 2618, a transmitting unit 2620,and a writing unit 2622.

In some embodiments, the processing unit 2606 is configured to enabledisplay (e.g., using the display enabling unit 2610) of a user interfacefor a financial application that is one of a plurality of applicationson the electronic device, where the financial application is athird-party application that is associated with a financial institutionand the financial application is restricted from accessing a securedarea of the device that is accessible by a first-party electronic walletapplication; while enabling display of the user interface for thefinancial application, receive (e.g., using the receiving unit 2612) arequest to add a payment account associated with the financialinstitution to the electronic wallet; and in response to receiving therequest to add the payment account associated with the financialinstitution to the electronic wallet and in accordance with adetermination that addition of the payment account to the electronicwallet has been authorized, store (e.g., using the storing unit 2614)information associated with the payment account that is provided by thethird-party application to the secured area of the device that isaccessible by the first-party electronic wallet application.

In some embodiments, the authorization is received from a user via auser input at the electronic device.

In some embodiments, the authorization is received from the financialinstitution.

In some embodiments, the processing unit 2606 is further configured toprior to storing information associated with the payment account that isprovided by the third-party application to the secured area of thedevice, receive (e.g., using the receiving unit 2612) user inputincluding user login information for the financial application.

In some embodiments, the user interface for the financial applicationincludes displayed details about the payment account associated with thefinancial institution.

In some embodiments, the processing unit 2606 is further configured toenable display (e.g., using the display enabling unit 2610) of a userinterface for the first-party electronic wallet application, thedisplayed user interface for the first-party electronic walletapplication including the details about the payment account associatedwith the financial institution.

In some embodiments, the processing unit 2606 is further configured toaccess (e.g., using the accessing unit 2616) the stored informationassociated with the payment account from the secured area of the device;and provide (e.g., using the providing unit 2618) the accessedinformation associated with the payment account to a purchasingapplication that is restricted from accessing the secured area of thedevice.

In some embodiments, the electronic device includes one or more wirelesscommunication elements 2604, the processing unit 2606 further configuredto access (e.g., using the accessing unit 2616) the stored informationassociated with the payment account from the secured area of the device;and transmit (e.g., using the transmitting unit 2620), using the one ormore wireless communication elements 2604, the information associatedwith the payment account to a payment terminal that is proximate to theelectronic device, where the information associated with the paymentaccount enables the payment terminal to engage in a payment transaction.

In some embodiments, the processing unit 2606 is further configured toprovide (e.g., using the providing unit 2618) the financial applicationaccess to a portion of the secured area of the device.

In some embodiments, the processing unit 2606 is further configured towrite (e.g., using the writing unit 2622) the information associatedwith the payment account into the secured area of the device.

In some embodiments, the processing unit 2606 is further configured to,in response to writing the information associated with the paymentaccount into the secured area of the device, provide (e.g., using theproviding unit 2618) an indication that the payment account has beenlinked to the device.

In some embodiments, the electronic wallet of the electronic deviceincludes one or more different payment accounts associated with a userof the electronic device.

The operations described above with reference to FIG. 19 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.26. For example, displaying operation 1902, receiving operation 1904,and storing operation 1906 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

What is claimed is:
 1. An electronic device comprising: one or morewireless communication elements; one or more input devices; one or moreprocessors; memory; and one or more programs stored in memory, includinginstructions which, when executed by the one or more processors, causethe electronic device to: receive, via the one or more wirelesscommunication elements, from a contactless payment terminal that isproximate to the electronic device, a request for loyalty accountinformation for a payment transaction for which authorization to proceedhas been provided via the one or more input devices of the electronicdevice; and in response to receiving the request for loyalty accountinformation: determine whether a loyalty-sharing condition is met; inaccordance with a determination that the loyalty-sharing condition ismet, transmit loyalty account information of a loyalty account to thecontactless payment terminal via the one or more wireless communicationelements; and in accordance with a determination that theloyalty-sharing condition is not met, forgo transmitting loyalty accountinformation of the loyalty account to the contactless payment terminal.2. The electronic device of claim 1, the one or more programs furtherincluding instructions for: prior to transmitting loyalty accountinformation of the loyalty account, determining that authorization toproceed with the payment transaction is provided, and whereintransmitting loyalty account information of a loyalty account to thecontactless payment terminal via the one or more wireless communicationelements occurs without requiring separate authorization.
 3. Theelectronic device of claim 1, the one or more programs further includinginstructions for: in accordance with a determination that theloyalty-sharing condition is not met and a loyalty sharing permissionregarding user instruction to provide the loyalty account information inthe absence of input specifying a different payment account before thedevice receives authorization to proceed with a payment transactionusing the device is not stored on the electronic device, providing analert requesting confirmation to provide the loyalty account informationto the contactless payment terminal.
 4. The electronic device of claim1, wherein the one or more input devices of the electronic deviceinclude a fingerprint sensor, the one or more programs further includinginstructions for: in accordance with the determination that theloyalty-sharing condition is not met and while detecting a fingerprinton the fingerprint sensor: providing a notification requestingauthorization to transmit loyalty account information of the loyaltyaccount to the contactless payment terminal; detecting, via the one ormore wireless communication elements, that the device has been removedfrom a field of the contactless payment terminal and replaced into thefield of the contactless payment terminal; and in response to detectingthat the device has been replaced into the field of the contactlesspayment terminal, determining that the fingerprint is consistent with anenrolled fingerprint that is enabled to authorize transactions; and inresponse to determining that the fingerprint is consistent with anenrolled fingerprint that is enabled to authorize transactions,transmitting loyalty account information of the loyalty account to thecontactless payment terminal.
 5. The electronic device of claim 1,wherein the one or more input devices of the electronic device include afingerprint sensor, the one or more programs further includinginstructions for: in accordance with the determination that theloyalty-sharing condition is not met and while detecting a fingerprinton the fingerprint sensor: providing a notification requestingauthorization to transmit loyalty account information of the loyaltyaccount to the contactless payment terminal; receiving user inputselecting a second loyalty account different from the loyalty account;detecting, via the one or more wireless communication elements, that thedevice has been removed from a field of the contactless payment terminaland replaced into the field of the contactless payment terminal; inresponse to detecting that the device has been replaced into the fieldof the contactless payment terminal, determining that the fingerprint isconsistent with an enrolled fingerprint that is enabled to authorizetransactions; and in response to determining that the fingerprint isconsistent with an enrolled fingerprint that is enabled to authorizetransactions, transmitting loyalty account information of the secondloyalty account to the contactless payment terminal.
 6. The electronicdevice of claim 1, wherein the one or more input devices of theelectronic device include a fingerprint sensor, the one or more programsfurther including instructions for: in accordance with the determinationthat the loyalty-sharing condition is not met and while detecting afingerprint on the fingerprint sensor: providing a notificationrequesting authorization to transmit loyalty account information of theloyalty account to the contactless payment terminal; receiving userinput declining to use the loyalty account; detecting, via the one ormore wireless communication elements, that the device has been removedfrom a field of the contactless payment terminal and replaced into thefield of the contactless payment terminal; in response to detecting thatthe device has been replaced into the field of the contactless paymentterminal, determining that the fingerprint is consistent with anenrolled fingerprint that is enabled to authorize transactions; and inresponse to determining that the fingerprint is consistent with anenrolled fingerprint that is enabled to authorize transactions,proceeding with the payment transaction without transmitting the loyaltyaccount information of the loyalty account to the contactless paymentterminal.
 7. The electronic device of claim 1, the one or more programsfurther including instructions for: in accordance with a determinationthat the loyalty-sharing condition is not met and a loyalty sharingpermission stored on the electronic device indicates user instruction tonot provide the loyalty account information in the absence of inputspecifying a different payment account before the device receivesauthorization to proceed with a payment transaction using the device,proceeding with the payment transaction using a payment account withoutprompting for confirmation.
 8. The electronic device of claim 1, whereinthe loyalty-sharing condition includes a condition that is met when theelectronic device has previously been authorized to provide the loyaltyaccount information of the loyalty account to the contactless paymentterminal.
 9. The electronic device of claim 1, wherein theloyalty-sharing condition includes a condition that is met when theelectronic device has previously been authorized to provide the loyaltyaccount information of the loyalty account to a different contactlesspayment terminal in a group of contactless payment terminals thatincludes the contactless payment terminal.
 10. The electronic device ofclaim 1, wherein the loyalty-sharing condition includes a condition thatis met when the electronic device has previously been authorized toprovide the loyalty account information of the loyalty account to one ormore contactless payment terminals within a predetermined geographicalregion in which the contactless payment terminal is located.
 11. Theelectronic device of claim 1, the one or more programs further includinginstructions for: prior to receiving the request for loyalty accountinformation, detecting a field of the contactless payment terminal; andprior to detecting the field of the contactless payment terminal,receiving, via the one or more input devices of the electronic device,the authorization to proceed.
 12. The electronic device of claim 1, theone or more programs further including instructions for: prior toreceiving the request for loyalty account information, detecting a fieldof the contactless payment terminal; and while detecting the field ofthe contactless payment terminal, receiving, via the one or more inputdevices of the electronic device, the authorization to proceed.
 13. Theelectronic device of claim 1, the one or more programs further includinginstructions for: after transmitting loyalty account information of aloyalty account to the contactless payment terminal via the one or morewireless communication elements for a predefined number of loyaltyaccounts, receiving a request for loyalty account information of asecond loyalty account from the contactless payment; and in response toreceiving the request for loyalty account information of the secondloyalty account from the contactless payment, forgoing transmittingloyalty account information of the second loyalty account to thecontactless payment for the payment transaction.
 14. The electronicdevice of claim 1, wherein the one or more input devices comprises afingerprint sensor and wherein the authorization was provided inaccordance with: detecting a respective fingerprint on the fingerprintsensor of the electronic device; and in response to detecting therespective fingerprint on the fingerprint sensor, determining that thefingerprint is consistent with an enrolled fingerprint that is enabledto authorize payment transactions.
 15. The electronic device of claim 1,wherein the one or more input devices comprises a touch-sensitivesurface and wherein the authorization was provided in accordance with:receiving a passcode via the touch-sensitive surface of the electronicdevice; and in response to receiving the passcode, determining that thepasscode is consistent with an enrolled passcode that is enabled toauthorize payment transactions.
 16. The electronic device of claim 1,wherein the payment transaction is conducted using a payment account ofan electronic wallet of the electronic device.
 17. The electronic deviceof claim 1, wherein an electronic wallet of the electronic deviceincludes loyalty account information for one or more different loyaltyaccounts associated with a user of the electronic device, the one ormore different loyalty accounts being different from the loyalty accountused for the payment transaction.
 18. The electronic device of claim 1,the one or more programs further including instructions for:transmitting, using the one or more wireless communication elements,payment account information to the contactless payment terminal, whereinthe payment account information enables the contactless payment terminalto engage in the payment transaction.
 19. A non-transitorycomputer-readable storage medium comprising one or more programs forexecution by one or more processors of an electronic device with one ormore wireless communication elements and one or more input devices, theone or more programs including instructions which, when executed by theone or more processors, cause the electronic device to: receive, via theone or more wireless communication elements, from a contactless paymentterminal that is proximate to the electronic device, a request forloyalty account information for a payment transaction for whichauthorization to proceed has been provided via the one or more inputdevices of the electronic device; and in response to receiving therequest for loyalty account information: determine whether aloyalty-sharing condition is met; in accordance with a determinationthat the loyalty-sharing condition is met, transmit loyalty accountinformation of a loyalty account to the contactless payment terminal viathe one or more wireless communication elements; and in accordance witha determination that the loyalty-sharing condition is not met, forgotransmitting loyalty account information of the loyalty account to thecontactless payment terminal.
 20. A method, comprising: at an electronicdevice including one or more wireless communication elements and one ormore input devices: receiving, via the one or more wirelesscommunication elements, from a contactless payment terminal that isproximate to the electronic device, a request for loyalty accountinformation for a payment transaction for which authorization to proceedhas been provided via the one or more input devices of the electronicdevice; and in response to receiving the request for loyalty accountinformation: determining whether a loyalty-sharing condition is met; inaccordance with a determination that the loyalty-sharing condition ismet, transmitting loyalty account information of a loyalty account tothe contactless payment terminal via the one or more wirelesscommunication elements; and in accordance with a determination that theloyalty-sharing condition is not met, forgoing transmitting loyaltyaccount information of the loyalty account to the contactless paymentterminal.